[LEAPSECS] Windows Time's "Great Leap Forward"

Matsakis, Demetrios matsakis.demetrios at usno.navy.mil
Fri Oct 9 11:02:45 EDT 2009


Microsoft's NTP package gives no notice of a pending leap second, even
when acting as a server. Here are some pastes from Microsoft's web
site:

"The Windows Time service does not indicate the value of the Leap
Indicator when the Windows Time service receives a packet that includes
a leap second. (The Leap Indicator indicates whether an impending leap
second is to be inserted or deleted in the last minute of the current
day.) Therefore, after the leap second occurs, the NTP client that is
running Windows Time service is one second faster than the actual time.
This difference is resolved at the next time synchronization."

"When the Windows Time service is working as an NTP server

No method exists to include a leap second for the Windows Time service."


See http://support.microsoft.com/kb/909614


More information about the LEAPSECS mailing list