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

2017-07-31 Thread Miroslav Lichvar
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"

2017-07-31 Thread Bryan Christianson
> 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"

2017-07-31 Thread Miroslav Lichvar
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