On Sat, 2019-11-23 at 08:59 -0500, Sam Varshavchik wrote:
I have chrony running and pointing to my ISP's time server, not
Fedora pool, so it's always the same NTP server.
This box is up 24/7, and I just rebooted it. And I get this, after a
Nov 23 08:53:10 shorty chronyd: System clock TAI offset set to 37 seconds
Nov 23 08:53:10 shorty chronyd: System clock wrong by -5.652285 seconds, adjustment
Nov 23 08:53:10 shorty chronyd: System clock was stepped by -5.652285 seconds
This was a reboot, and not a shutdown.
Some PCs don't keep time well, and that can account for one PC being
different from the others, regardless of CMOS battery condition.
When I was setting up a new server, I looked into the NTP versus
chronyd thing, and came to the following conclusions.
NTP was better for computers that were continuously running. It keeps
tinkering with the clock to keep it on time. And NTP has a long
history, lots of things support it, and has well known behaviour.
Chronyd was better for computers are shutdown. It's designed to
quickly reset your clock, but didn't continually tinker with it (that
may be configurable, and I don't know what it's future behaviour will
be). It's newer, and supposedly less widely supported.
Linux 3.10.0-1062.4.3.el7.x86_64 #1 SMP Wed Nov 13 23:58:53 UTC 2019 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.