| Re: [chrony-dev] Bug in chronyd -q "server ip" |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Bug in chronyd -q "server ip"
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Mon, 31 Jul 2017 21:46:19 +1200
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a1-4; h=Feedback-ID:X-Smtpcorp-Track:Message-Id:To:Date: Subject:From:Reply-To:Sender:List-Unsubscribe; bh=gga7+BjYwysF8prJ5lH3kxuOokc0SOIzhXK6u3axyxM=; b=H5w2SjMhKl/Vr7jIaFqZMG4wwk 5LJrc3T+LxcBXSXzMTKdkrkRPDhu3kU3bEyNcjMOGa/P4Ux7TGx7yYsbOKB/fneuL+bZhyHefj0Z/ gi53bDnX5fVwur1dNPQ+oIlVy4feX+6v9hLHKFDOCrvu8CbctCovn1ccJt6c3fXUj1WcD5P5fToM8 ZfLv9G/yfFheE9MWlZMZG3mmnWUJ3CNHrnhmiyAm+xb9k+mDmqs6SwtHWFwDhgMbPQ3io05fTuI/t ZmIumI+Opi2tXalJfSdyFxYi720cTdgyS/QwKRcYa6rxvu52x0rOdpwee4kKE1XGQ93bS+8QZyywn E8p6iZQw==;
- Feedback-id: 149811m:149811acx33YQ:149811saAXnyGDJg:SMTPCORP
> On 31/07/2017, at 8:32 PM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> 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 ?
Bryan Christianson
bryan@xxxxxxxxxxxxx
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.