Roger Oberholtzer wrote:
On Thu, Jan 5, 2017 at 3:44 PM, Carlos E. R.
wrote: My read is that the kernel has the leap second (hard/soft)coded into it somewhere. 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 don't think the kernel needs this information or even knows about leap seconds.
Yep, I agree.
When using ntp, the kernel just does what it is told. ntp decides how to change the time. The info that tells that a leap second is soon to happen lets ntp update that change in a possibly different way than how it handles normal jitter. How ntp does this is configured.
See maybe leapsmear - README.leapsmear
This is sort of what my original question was addressing: who adds the leap seconds? gpsd or ntp/chrony or the kernel? Does NTP have the leap seconds built in? Or does the ntp packet tell this? I think that is the case.
That is certainly the case on my setup. The leap second is announced by DCF77, and acted upon by ntpd.
The bigger mystery to me is strptime(3),
It seem to me that strptime() does just what we ask of it - convert a text timestamp to a "struct tm". It doesn't need to know much about anything? -- Per Jessen, Zürich (-2.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org