On 03/01/17 14:32, Carlos E. R. wrote:
31 Dec 02:38:57 ntpd[1749]: kernel reports leap second insertion scheduled 1 Jan 01:03:31 ntpd[1749]: kernel reports leap second has occurred 1 Jan 01:03:31 ntpd[1749]: kernel reports leap second has occurred
So ntpd is told by the kernel what is going to happen, 22 hours before.
Now, the next step is learning what happens at a stratum one server.
Depends on what software the server is running ... (afaik). The consensus (because the standard specifies 60 seconds per minute) is that 23:59:59 should happen twice. This relies on the server setting the warning, and the client acting on it. BUT WATCH OUT. I gather some time servers - Google in particular - accumulate a deliberate error (presumably of about .0003s/s) over the preceding day so that come midnight the clock is one second slow and the leap second puts it right. Which is fine UNTIL you need to be able to measure seconds accurately! The big problem is out current clock definition cannot cope with a 61-second minute, so all we have is ad-hoc fixes. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org