Carlos E. R. wrote:
On 2017-01-05 10:11, Per Jessen wrote:
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.
In my server, it is obvious that is what happened:
Jan 01 00:59:59 Isengard kernel: Clock: inserting leap second 23:59:60 UTC
(the kernel reports that it inserts...)
Sure, but that is after being instructed to do so by NTP.
And the ntp log confirms:
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
About 22 hours before, the kernel tells the ntpd daemon that it is going to insert a leap second,
Uh no, that's not really it. ntp has called ntp_adjtime() and the return code indicates ("kernel reports") that a leap second is going to be inserted. ntpd just writes a log message to indicate that.
and later it says that the kernel did in fact insert it, but at 01:03:31 - it could be that ntp log is using GPT time, not local time.
Yes it is.
My read is that the kernel has the leap second (hard/soft)coded into it somewhere.
ntpd has the known leap seconds hardcoded in some test utilities, but obviously cannot have any future ditto. The kernel has nothing, to my knowledge.
After all, the time function has to be able to do time counting calculations taking into account all the historic variations of the clock.
I'm not sure it does. If you run a system without ntpd, and instead relying only on the RTC, you'll end up with a clock way out of touch with reality, that's all :-) -- Per Jessen, Zürich (-0.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org