| 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: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 31 Jul 2017 10:32:56 +0200
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C93EFDBE81
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 option was intended more for cases where chronyd shouldn't be
running continously.
> 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?
--
Miroslav Lichvar
--
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.