On 2017-01-05 16:57, Roger Oberholtzer wrote:
On Thu, Jan 5, 2017 at 4:39 PM, Carlos E. R. <> wrote:
This can be proved by running an isolated test machine without ntp, and setting the time on it to Dec 31th, see what happens in the log. My bet is it adds the leap second.
Interesting test. I think it will not add the leap second. It may also interact with the setting that tells if the hardware clock is UTC. Things like daylight savings time changes only seem to be done when the hardware clock is set to UTC.
Yes, the handling of the CMOS clock is different when it doesn't keep UTC, and it was changed not many releases ago. It must be mentioned on one of the release notes. I don't remember right now, I still have some flu. Not fever.
One more question: at 00:00 local or UTC?
I think 00:00 UTC time. The full message was:
2017-01-01T00:59:59.001885+01:00 acme kernel: [1438619.838798] Clock: inserting leap second 23:59:60 UTC
Ah, yes.
My system changed the time at 00:59:59.001885 local time, which is 23:59:60 [sic] UTC
So the second must be inserted at the same instance everywhere: 23:59:60 UTC, no matter the local time.
Right. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)