(X-posted)
Did anyone notice the leap second added today? My boxes handled this correctly:
Clock: inserting leap second 23:59:60 UTC
It would have happened at 5:30 AM on 1st Jan in India (midnight UTC).
The real question is applications. Do you have any application that
does something like:
if (second < 0 || second > 59) {
fprintf (stderr, "Error!\n");
}
Then you do have a potential bug in the application.
If you have a tzdata package (or rather, /usr/share/zoneinfo/UTC file)
that was distributed after 4th July 2005 (my RHEL tzdata RPM was
updated on July 15th for the leap second), then your system probably
handled this correctly
(http://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat).
I skipped all the new year parties so that I could be in the
datacenter at 1AM (I am in CET, which is UTC+1h), to click a photo of
my NTS200 display when it shows 23:59:60. But alas! I clicked the
camera a second too soon, and all I got was the mundane everyday
23.59.59 :((
Binand
