[chrony-dev] [PATCH] chronyd -q does not step the system clock

Attempting to step the system clock by using the -q option with chronyd would fail. --- main.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/main.c b/main.c index 5c6a281..b93a883 100644 --- a/main.c +++ b/main.c @@ -448,8 +448,13 @@ int main sched_priority =

Re: [chrony-dev] Bug in chronyd -q "server ip"

On Mon, Jul 31, 2017 at 09:46:19PM +1200, Bryan Christianson wrote: > >> Setting the option sets > >>clock_control = 0; > >> > >> In SYS_Intialise(), only the null driver is loaded. The actual system > >> drivers are not loaded. > >> > > Good catch. Would you like to submit a patch? >

Re: [chrony-dev] Bug in chronyd -q "server ip"

> On 31/07/2017, at 8:32 PM, Miroslav Lichvar wrote: > > On Mon, Jul 31, 2017 at 05:08:33PM +1200, Bryan Christianson wrote: >> I was just looking at using the -q option before actually running the daemon. > > Have you considered using the initstepslew directive? I'm

Re: [chrony-dev] Bug in chronyd -q "server ip"

On Mon, Jul 31, 2017 at 05:08:33PM +1200, Bryan Christianson wrote: > I was just looking at using the -q option before actually running the daemon. Have you considered using the initstepslew directive? I'm assuming you want to delay starting something before chronyd has stepped the clock. The -q