I was distracted and didn't look at my watch at midnight. I don't think it counted the leap—it's now off from my computer by one second. Apparently, my computer did it's leap second jump earlier in the evening, which is also rather disappointing:
Dec 31 19:08:13 3po ntpd: no servers reachable Dec 31 19:19:30 3po ntpd: synchronized to 184.108.40.206, stratum 2 Dec 31 19:19:30 3po ntpd: time reset -1.000308 s Dec 31 19:23:47 3po ntpd: synchronized to 220.127.116.11, stratum 2
I didn't think that was supposed to happen, but I guess the leap second actually occurred at midnight UTC rather than midnight local time. Of course, midnight UTC was at 18:00 local time, so I wonder why it took over an hour for the reset to happen...
Update: Aha! It's a bug (maybe).Posted by mike at January 1, 2006 12:51 AM | Internet