You are not logged in.
NTPd tries to minimize the time deviation to less than 10 milliseconds by repeated requests to other servers. If I see things correctly timesyncd requests the network time only once during startup. Is this the desired behavior or a bug?
Offline
I don't think timesyncd only requests the network time only once but do it "intelligently. According to the following website: http://time.is/ , my time is always exact with timessyncd enabled. So I assume it works correctly.
Last edited by olive (2016-11-17 16:09:01)
Offline
I don't think timesyncd only requests the network time only once but do it "intelligently. According to the following website: http://time.is/ , my time is always exact with timessyncd enabled. So I assume it works correctly.
Sorry, my question is obscure without some context. I compared the network traffic between a Mac and an Archlinux system. What I detected was a deviation between NTP calls. The Mac updated its system-time frequently whereas Archlinux queried the 2.arch.pool.ntp.org only once. I would expect that at least two calls are necessary to detect any errors.
Last edited by yousry (2016-11-17 17:40:58)
Offline