[LEAPSECS] Leap seconds ain't broken, but most implementations are broken
Martin Burnicki
martin.burnicki at burnicki.net
Sun Jan 8 10:30:48 EST 2017
Zefram wrote:
> To be clear: obviously knowledge of the upcoming leap second must come
> from some external source. A system with such advance knowledge is then
> able to apply that knowledge at the proper time, maintaining a correct
> clock through the leap second, without any further external contact.
> It doesn't have to be told that the leap second has arrived. This kind
> of knowledge is exhibited by some Unices, but not by Windows.
That's exactly the point, IMO.
Martin
More information about the LEAPSECS
mailing list