> On 31/07/2017, at 8:32 PM, Miroslav Lichvar <mlich...@redhat.com> 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 assuming you
> want to delay starting something before chronyd has stepped the clock.
initstepslew should do what I want which is to step the clock if the initial
offset exceeds a threshold. Thanks for that.
I'm having an issue with VirtualBox macOS VMs being about 5 seconds off when
they start. They seem to take a long time to do the EFI boot and it looks as
though the clock is stalled while that's going on.
>> It appears to be broken.
>> 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?
I'm not sure what the patch would be. Only set clock_control = 0 for -Q
option but leave at 1 for -q ?
To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe"
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the
Trouble? Email listmas...@chrony.tuxfamily.org.