On 2016-02-06, Lampshade <lampsh...@poczta.fm> wrote: > 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
> I don't think that clock is adjusted "by" that values. It is. > If that would be the case, I guess clock would be far faster synced. The clock isn't set, it is adjusted with adjtime(2). That takes time. The maximum clock skew rate is 5 ms per second. Let's look at the numbers above. From 17:58:17 to 18:02:02, 225 seconds have passed. The clock can be adjusted by 1.125 seconds in that time. Which is the difference in the logged adjustment values. -- Christian "naddy" Weisgerber na...@mips.inka.de
