Messages in this thread | | | Date | Wed, 07 Jan 2009 20:48:11 +1030 | From | David Newall <> | Subject | Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009 |
| |
Alan Cox wrote: > As far as the kernel and leapseconds go - remember the kernel RTC support > does not know about leap seconds >
True but irrelevant because the RTC returns a timestamp. And it's quietly understood that the RTC is only an approximation.
The remaining fly in the ointment, if indeed the NTP client doesn't already do what I've outlined, is that leap seconds aren't reckoned into NTP broadcasts. As intimated, this is correctable using leap second information from zoneinfo.
Even though this is manifestly not a kernel issue, I'll work up a patch for ntpdate (apparently what I use) and post her, which I'm sure will be useful for all other NTP clients.
However it is now clear that no special kernel support is required for leap-seconds, and any such code that's been incorporated needs to be removed. Removed I say!
| |