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?

> - ...
> 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.

> 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.

> 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.

Miroslav Lichvar

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.

Reply via email to