Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009

Chris Adams
2009-01-03T07:00:44Z

Once upon a time, David Newall <davidn@davidnewall.com> said:
> I don't understand this idea, nor the patch for the problem. I don't
> see why adding a leap second would impact the kernel in any way.
> Shouldn't this be a simple zoneinfo change, whereby the last two seconds
> of the year (in each timezone) both map to 31dec2008 23:59:59? That's
> the way the change has worked in the real world. Why would ntp or the
> kernel be involved?

The leap second isn't a simple thing like a time zone. Zones account
for an offset from UTC, but a leap second is an extra second inserted
into (or possibly removed from) UTC itself. There was actually a 61
second minute on Dec. 31. The trouble comes in keeping the "seconds
since the epoch" counter sane, meaning (seconds % 86400) == 0 at
00:00:00 UTC. Since there were 86401 seconds Dec. 31, the kernel had to
tick the last second twice to keep correct UTC time.

NTP is used to distribute and synchronize time information, including
leap second info.

See Wikipedia and Google for more information.
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.