|Re: [chrony-users] Fwd: Chrony malfunctioning at beaglebones|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Fwd: Chrony malfunctioning at beaglebones
- From: Nuno Gonçalves <nunojpg@xxxxxxxxx>
- Date: Thu, 8 Oct 2015 00:35:52 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=hyG7mMATpmkAGZOqI9GZXuRUs5f3uYQHYjKHoUzxWuE=; b=xdB+IyAORuTOLmi3fuEQCSvPJxs90+wPoXyguGTEDrUd5O8Ujfw9jbDj2vvLAg+AaC 7KMyXPToS9a23DivWFktusuHiDM/ViLRTaoBxd+rRHNyvB0BkBE6tBTqNSdlpAAkQomI EkdQpzivqTB7WCrmP34qCaNPj7z4ZoGTW2K6AzcGsC+kvSnlrlHWeecM2wqvLPaf1/zq 2NlpoeSGIeopRlSOm/2jGyDcwc5sAgdphD7LHF1qmkZhIB6kFVdDe8axy76sPnzOo9v4 T4Xc84qqx7s2QuRd2v3CrAdJzo+FHlMSfdXFLynj4eWhdPD5EXtzH5ggaYmPc4cOIEA3 FemA==
On Tue, Oct 6, 2015 at 11:53 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> I have some code ready for this, but I realized if there is some
> interval in which the driftile timestamp is ignored, it will not work
> when the chrony RTC tracking (rtcfile) is enabled. When the RTC time
> is reset to its initial value and corrected by the previously measured
> offset, it may still be in the allowed interval before the driftfile
> modification time and it will be ignored. It would be basically
> restoring time of the previous boot.
> I'm not sure if we can make any assumptions on the raw RTC time if
> rtcfile is enabled, it's perfectly ok to keep it in 1970 and rely on
> chrony to correct the offset.
> So, should we always restore time from the modification timestamp of
> the driftfile with -s if it's in future and log a warning when the RTC
> time is ignored to make it easier for the user to debug any unexpected
Sorry for the delay. Had to read it a few times to understand. Chrony
is not so simple as we, users, like to think.
I see you already implemented it, anyway here go my comments, also
because I noticed I made a mistake previously.
I wrongly assumed that a rtc change by other OS to another timezone
should be respected. It shouldn't. If chrony detects the RTC is behind
its driffile by 8 hours, what does that mean? Nothing. Because Chrony
can never figure out what is the actual UTC time it means, only some
time from some random timezone.
So it is only the DST changes that can be more or less safely
inferred, and not so hardly:
IF driftfile over 1 hour ahead THEN restore time from driftfile
ELSE IF driftfile up to 1 hour ahead THEN IF not DST change at the end
of current driftfile hour, restore time from driftfile
ELSE restore time from RTC
In regard to rtcfile, I didn't check how you implemented it, but I
would say if the configuration have it, we could disregard this sanity
checks and always restore from the RTC as it is. Is really doesn't
make sense for the user to configure rtcfile if then he doesn't trust
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.