On 2019-11-23 22:22, Tom Horsley wrote:
On Sat, 23 Nov 2019 08:59:02 -0500
Sam Varshavchik wrote:
> Anyone know where to investigate this further?
The linux app that syncs to the hardware is "hwclock" (which
has various obscure parameters described in the man page).
You could make a script to sync with hwclock then reboot
and see if the time is more in sync when it comes back.
That would verify it isn't being synced (but, unfortunately,
wouldn't help track down where the hwclock call ought
to happen).
Maybe add an ExecStop= option to the chronyd.service with the appropriate parameters?
FWIW, on my rather old HP system I too get "System clock wrong" on some (not
all) reboots.
A quick look and I estimate the average for this system is about 6 seconds.
The discrepancy is noted within 2 seconds of boot. I wouldn't have noticed it if Sam
hadn't
pointed it out.
--
The key to getting good answers is to ask good questions.