012345678901234567890123456789012345678901234567890123456789 It is probably just aesthetics. When I have clock not synchronized and differs a few seconds, I have following output: grep ntpd /var/log/daemon | tail -n 30 Feb 6 17:57:00 host ntpd[7585]: constraint reply from ip: offset 8.928573 Feb 6 17:57:19 host ntpd[7585]: peer 158.75.5.245 now valid Feb 6 17:57:23 host ntpd[7585]: peer 194.29.130.252 now valid Feb 6 17:57:25 host ntpd[7585]: peer 150.254.183.15 now valid Feb 6 17:58:17 host ntpd[9279]: adjusting local clock by 9.096751s Feb 6 18:02:02 host ntpd[9279]: adjusting local clock by 7.971861s Feb 6 18:05:50 host ntpd[9279]: adjusting local clock by 6.838999s Feb 6 18:07:26 host ntpd[9279]: adjusting local clock by 6.363730s Feb 6 18:07:59 host ntpd[9279]: adjusting local clock by 6.196142s Feb 6 18:11:11 host ntpd[9279]: adjusting local clock by 5.246003s Feb 6 18:13:18 host ntpd[9279]: adjusting local clock by 4.615421s Feb 6 18:14:55 host ntpd[9279]: adjusting local clock by 4.133148s Feb 6 18:15:43 host ntpd[7585]: peer 150.254.183.15 now invalid Feb 6 18:15:44 host ntpd[9279]: adjusting local clock by 3.892080s Feb 6 18:20:04 host ntpd[9279]: adjusting local clock by 2.597929s Feb 6 18:21:02 host ntpd[7585]: peer 150.254.183.15 now valid Feb 6 18:24:19 host ntpd[9279]: adjusting local clock by 1.321471s Feb 6 18:24:51 host ntpd[9279]: adjusting local clock by 1.161470s Feb 6 18:29:06 host ntpd[7585]: clock is now synced
I don't think that clock is adjusted "by" that values. If that would be the case, I guess clock would be far faster synced.
