Re: [chrony-dev] [PATCH v3] main: add -X to fall back if time is not adjustable

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-dev Archives ]




On Tue, Mar 13, 2018 at 2:50 PM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
On Tue, Mar 13, 2018 at 12:17:41PM +0100, Christian Ehrhardt wrote:
> The important part is the lack of knowledge of the target systems
> capabilities.
> They are:
> - not detectable by some install paths, for example
>   - install in VM with behavior A onto phys disk but reboot host into said
> disk
>   - installing on a remote disk mounted chroot, which might be totally
> different when this runs.
>   - ...
> - Several tools/configs might add/remove capabilities from a system later
> on in the lifecycle
> - Some move machines between places with different capabilities

Does any of this change the requirement on synchronization of the
system clock?

Something has to install and configure the chronyd service to run as
an NTP server on the system. (By default it's just a client.) What
does decide if -x/-X is added to the options?

For above cases the example would be a tool that needs time synchronization, pulls in chrony but the tool wants to ensures it runs wherever it ends up (with clock sync if it can, but at least the NTP server part if it can't).

There are even discussions ongoing if for Ubuntu we would want to default to -X in general (as default in a config file).

> - ...
> The TL;DR of the "motivation" is: the inability to decide if using "-x" is
> right or not (at any time).

I think the same applies to -X.
 
No it's not.
The users that started this with a Launchpad bug would always set -X for their case.
They would never want to set "-x" or "", but "-X" would be just what they want.

> With just "-x" available this leads to one of the following:
> A) So if one sets "-x" it will NEVER sync the clock even if the system
> would be capable to do so.

The system may be capable, but nothing requires the clock to be
synchronized, right? Otherwise it would make no sense to use any of
the -X/-x options.

Partially correct, nothing "hard requires" the clock to be synced, but it is "preferred" to sync it if possible so setting -x would waste that.

> BTW - in case it might be better to discuss interactive - I'm "cpaelzer" on
> freednode IRC.
> If there is a common place chrony matters are usually discussed (other than
> the ML) that would be nice to know - I haven't found a hint about it on the
> web page.

I'm mlichvar on #ntp. People discuss chrony there occasionally.

Thanks, will join there shortly to hopefully get our intentions fully clear in a discussion there. 
 
--
Miroslav Lichvar

--
To unsubscribe email chrony-dev-request@chrony.tuxfamily.org with "unsubscribe" in the subject.
For help email chrony-dev-request@chrony.tuxfamily.org with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxx.org.




--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/