Louis Lagendijk writes:
On Sat, 2019-11-23 at 10:09 -0500, Sam Varshavchik wrote:
> So, hwclock must be getting synced. But I don't see where hwclock
> would be
> getting called from. grepping /lib/systemd/system finds nothing.
> hwclock
> itself comes from util-linux, which doesn't install anything there.
>
Is chrony itself supposed to keep the hw clock synced?
From
https://chrony.tuxfamily.org/manual.html#rtcsync-directive::
4.2.55 rtcsync
The rtcsync directive enables a mode where the system time is
periodically copied to the real time clock (RTC).
That looks like it. The rtcsync directive exist in my chrony.conf. I didn't
put there, so it must be in the default chrony.conf
So, the hardware clock seems to be getting synced, but it loses some seconds
during a reboot.
This server gets rebooted on a regular schedule, and the default rotation of
/var/log/messages captured last five reboots, and showed that only the three
of them resulted in a skewed system clock:
Oct 20 09:43:00 shorty chronyd[1080]: System clock wrong by -13.429737 seconds, adjustment
started
Nov 16 06:50:35 shorty chronyd[1068]: System clock wrong by -6.621246 seconds, adjustment
started
Nov 23 08:53:10 shorty chronyd[992]: System clock wrong by -5.652285 seconds, adjustment
started
The logs of chronyd starting on Nov 2nd and Nov 9nd did not log any time
adjustment.
Next time I cycle it, I'll check what the hwclock reports, before the
reboot. Which should be current, if chrony is truly syncing it.