Sample Header Ad - 728x90

How to prove that NTP time sync is checking regularly

1 vote
3 answers
153 views
How does one prove that systemd-timesyncd is regularly polling the NTP servers to ensure that the system's clock remains "synchronized"? I understand that I can check the *yes/no* sync'd status by running timedatectl, and it does tell me 'yes', but couldn't that just be a stale status from months prior? I don't see any evidence that any software component is actually reaching out to the NTP server pool to actually check on a regular basis. With the default config PollIntervalMaxSec of 2048, it's my understanding that it should reach out to NTP, at most, every 34 minutes to do a clock comparison. Is this how it should work? If I run journalctl -u systemd-timesyncd I only see evidence of sync events for reboots or apt upgrades. In fact, weeks go by without any clock synchronization log entries. For my time-sensitive application, I'm concerned that if weeks/months go by without any NTP checking, my system's clock can drift perhaps significantly. I'd like it to check once a day and *prove* that it is.
Asked by BCA (113 rep)
Mar 19, 2025, 02:24 PM
Last activity: Mar 19, 2025, 10:09 PM