Re: [chrony-dev] [RFC] Transparent fallback from NTP reference clock to RTC

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





Miroslav Lichvar schrieb am Donnerstag, 3. Juli 2025 09:19:17 (+02:00):

> On Wed, Jul 02, 2025 at 09:59:39PM +0200, Christoph Schittel wrote:
> > Could you add an option to force STA_UNSYNC when reaching a settable limit? > > Can you please explain the use case? > At the time the limit of 16s was implemented in the kernel, this was an reasonable choice. Today for many applications even a (possible) deviation of 1s or less may be regarded as too big and the system should be signaling it by setting STA_UNSYNC. Reading David R. Mills documentation reads like the syncing service should set STA_UNSYNC. The kernel setting it, when maxerror reaches 16s was just meant as last resort.

(Remote) monitoring services could benefit, because hosts with sync problems could be very easily detected. E.g. NAGIOS instead monitors the clock difference between itself and remote hosts. This implies the monitoring host has the "right" time. This could be improved by reading remote hosts STA_UNSYNC, if it will be set when needed (which should be the admin's choice, not the kernel's).

regards,
Christoph

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


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