Le 08/07/2020 à 14:36, Dave Howorth a écrit :
From https://en.wikipedia.org/wiki/Network_Time_Protocol "The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving a time scale that rolls over every 232 seconds (136 years) and a theoretical resolution of 2−32 seconds (233 picoseconds)."
for sure 2^32 fore each
public Internet, and can achieve better than one millisecond accuracy
that have little meaning. With the present (and for what I know also future :-) light speed limit, the fiber light spend around 13ms to go to/from my next internet link (minimum ping). so the accuracy of the atomic clock have to be modified by the time between it's position and mine. How can one achieve this? May be a GPS knowing the respective position of the satellite and the receiver can make a fix, but on internet? it can only give legal time not the precise time I have here on an unknown position
According to https://en.wikipedia.org/wiki/WWVB WWVB broadcasts once every second so its precision is 1 second. It broadcasts 60 bits per second, so that's the limit of resolution.
if the time is casted every second, it can anyway be as precise as you want if the local clock is reasonably good, it wont derive so much in one second jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org