Roger Oberholtzer wrote:
If one reads about the Windows NTP client, it says that during the day the packets from the server (NTP - so it could be a Linux server) will indicate that a leap second should be done that day. But the Windows client ignores this. So, for a bit of time the client may be off by one second. But the next time sync corrects this and all is okay.
I would expect a local client to be sync'ed all the time - our time server uses DFC77 as a source, and if/when reception deteriorates, it will fall back to a stratus 1 server. When that happens I see a sync event in the logs: 3 Jan 00:28:14 ntpd[21087]: synchronized to 162.23.41.10, stratum 1 3 Jan 00:36:50 ntpd[21087]: synchronized to GENERIC(0), stratum 0
Which implies that the server initially tells that a leap second is soon to happen. Then, at some point, the leap second is incorporated into the time.
The DFC77 signal has a leap second warning bit, afaik it is set during the hour before the leap second. Not sure what ntp does with it, presumably it's in the protocol: http://www.ntp.org/ntpfaq/NTP-s-algo-real.htm#AEN2499 -- Per Jessen, Zürich (-0.5°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org