Carlos E. R. wrote:
ntp log has this:
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.
That does not make much sense - unless the kernel had been told in advance. The messages above are reports on ntp_timeadj() return codes when ntpd attempts to adjust time. On 17 December, our time server was informed that a leap second is scheduled: from /var/log/ntp: 17 Dec 01:40:00 ntpd[21087]: PARSE receiver #0: STATE CHANGE: LEAP ADD WARNING; TIME CODE; (LEAP INDICATION; ANTENNA) -> TIME CODE; (LEAP INDICATION; ANTENNA) "LEAP ADD WARNING". Newer clients reported "second insertion scheduled" between 10 and 20 hours earlier. Most clients said nothing. The leap second itself was announced one hour before it was due. This is with DCF77.
Now, the next step is learning what happens at a stratum one server.
Roughly the same thing. The above is a stratum 1 server, -- Per Jessen, Zürich (-1.5°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org