Tom Horsley writes:
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).
I would expect that something would already be doing that.
Or maybe just replace the cmos battery on the motherboard and see if it get better :-).
Checking some other boxes I just rebooted, only this one is griping about the clock.
All these boxes are up 24/7. The longest they've been without power is about a week, when power's been out after a hurricane. Plus an occasional day of downtime, every other year or so, when power goes out for other reasons.
Some of those boxes are just as old as this one. Something has to be syncing the system time to the hardware clock on a reboot, otherwise their clocks would've drifted just as much. Maybe the other motherboards don't drain the battery at all when system power is on, and this one does.
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.
Attachment:
pgpUkepjI5uJf.pgp
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
