First off, Happy Canada Day. (eh? ;)

Lots of talk today about the 'Leap second bug' that caused various site and software crashes (see this post via CNET)...


"The adjustment, which was made by International Earth Rotation and Reference Systems Service, was necessary to keep atomic clocks in line with the Earth's ever-changing speed of rotation. Dozens of leap seconds have been added since their introduction in 1972."

Once again, The Extra Second was too much for some sites. Sounds like a new James Patterson crime novel. Or perhaps a new thriller from our own Mark Russinovich... I prefer his writing more these days anyway.

As I noted a couple of years ago, you'll find more documenting the impact of a leap second in Microsoft Knowledge Base (KB) article 909614, How the Windows Time service treats a leap second (as Michael Kaplan noted in his most excellent post)... 

"In short, W32Time does not account for a leap second being dependent on the NTP server. Most applications and services may be unaffected, but sysadmins and IT professionals should know that the leap second is not addressed until the next time sync following the official addition/ subtraction of the leap second.  Consumers really have nothing to worry about save questioning whether or not the time is accurate as broadcast during Dick Clark's New Year's Rockin' Eve when the crystal ball drops in Times Square.






Bookmark and Share

Also available via