|Re: [chrony-users] Fwd: Chrony malfunctioning at beaglebones|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On Fri, Oct 02, 2015 at 07:43:05AM -0400, Paul Carlisle wrote:
> On 10/02/2015 07:32 AM, Miroslav Lichvar wrote:
> >It would be nice if chronyd detected that automatically, but I'm not
> >sure what would be the best approach. I was considering to always
> >check if the system time is 1970-01-01 or 2000-01-01, but someone said
> >on a different mailing list there are other dates the system clock
> >would have after initialization from an RTC without battery.
> >Suggestions are welcome.
> Can you read the hardware clock twice, say 1.5 seconds apart, and note if
> the time has increased? If it hasn't, or if the read fails, it seems pretty
> certain the hardware clock is busted.
In the reports I've seen the RTC was working as expected, but it's
reset on every boot to a particular date depending on how the initial
value is interpreted by the kernel.
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.