Re: [chrony-users] Fwd: Chrony malfunctioning at beaglebones

[ Thread Index | Date Index | More Archives ]

Regarding this thread issue, it was indeed a kernel problem that has
been tracked down by now:

On Tue, Aug 18, 2015 at 10:07 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> The -s option can be useful for that. When there is no RTC, it will
> set the time from the modification time of the driftfile so the time
> at least will stay monotonic across reboot.

I am having difficulties using this -s option to restore time to
chrony.drift write time.

debian@radarcape-black:~$ ls -la /var/lib/chrony/chrony.drift
-rw-r--r-- 1 root root 42 Sep  5  2015 /var/lib/chrony/chrony.drift

debian@radarcape-black:~$ sudo /usr/local/sbin/chronyd -d -s
2000-01-01T00:03:33Z chronyd version 2.1.1 starting (+CMDMON +NTP
2000-01-01T00:03:33Z Frequency 49.334 +/- 0.011 ppm read from
^C2000-01-01T00:03:36Z chronyd exiting
debian@radarcape-black:~$ date
Sat Jan  1 00:03:37 UTC 2000

Maybe this feature also requires some settings at the configuration
file like "rtcfile"? I've read the documentation and it is not clear.


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.

Mail converted by MHonArc 2.6.19+