[email protected] (Danny Mayer) writes: >Folkert van Heusden wrote: >>> I don't recall ever seeing a report of NTP causing problems with normal >>> operations. >> >> Sorry for being anal on this but: >> Well almost: certain versions of the linux kernel under certain specific >> conditions would panic when ntp introduces a leap second. >> http://markmail.org/message/dhm5byrbfcarpiet?q=leap+second+list:org.kernel.vger.linux-kernel >> Ok it's a bug in the linux kernel but it is only triggered by ntp.
No, it is triggered by anything which uses adjtimex with the leapseconds flag set. >> >I just saw something about this in the NTP WG from the linux kernel >wranglers who seem to be totally confused about NTP. They should fix the >kernel bug and not start talking about TAI. They certainly should fix the bug. And they certainly seem totally confused about the definition of UTC. They do have a valid point, that has long long been debated in NTP forums re whether the Unix computer clock should show TAI or UTC. That is a valid debate to have (again). Of course it is trivial to convert from one to the other, assuming you have the leapseconds file. Of course if the unix system time were TAI then the leapsecond issue would not arise as far as the kernel were concerned. It would be cleaner to have the kernel on TAI and the translation to user space time via zoneinfo using a leapseconds file. >Danny >> >> Folkert van Heusden >> _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
