| Re: [chrony-dev] [RFC] Transparent fallback from NTP reference clock to RTC |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [RFC] Transparent fallback from NTP reference clock to RTC
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 2 Jul 2025 15:08:19 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1751461706; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=47EFUSSsNPx7WOr7IxfMWMC0KJ7fWMoY1LfE/v0tQVg=; b=R9WFSETSlRL9j21O6BuNlDZWVznYAgUdgkOwmbzr8V6YcawByPPhXnVooyh9pG77tqzfo7 9oHPNdHCNPVwm/YxoRmrvc7r4ezL+B6TvNWF8DqkPEhkVTWziir401WWcGq2XEGKdnEK3W xa50W2P1dW4vMFMGN2OlIxtmzWUDX/E=
On Wed, Jul 02, 2025 at 02:55:02PM +0200, Ahmad Fatoum wrote:
> > chronyd does not set the STA_UNSYNC flag when it loses its upstream
> > sources.
>
> Oh. Then I have trouble understanding the code in set_sync_status, which
> compares max_error against MAX_SYNC_ERROR (== 16s) as it looks like that
> would cause STA_UNSYNC to be set once the threshold is exceeded.
16 seconds is the maximum value that the kernel can keep as esterror
and maxerror. It would automatically set the STA_UNSYNC flag if the
application didn't set it. Normally, if the clock is well
synchronized, it takes a few days for that threshold to be reached. I
assume you are interested in much shorter intervals.
--
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.