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.
In message 20091009153241.gi20...@fysh.org, Zefram writes:
Matsakis, Demetrios wrote:
Microsoft's NTP package gives no notice of a pending leap second, even
when acting as a server.
No great surprise. Microsoft really doesn't get NTP.
s/NTP/time at all/
--
Poul-Henning Kamp | UNIX
Steve,
Steve Allen wrote:
Within the recent CGSIC proceedings is the overview presentation by
Lewandowski of the BIPM.
http://www.navcen.uscg.gov/cgsic/meetings/49thmeeting/Reports/%5B39%5DTiming_WL_General.pdf
It includes one page plotting the various satellite time scales and
another showing
AFAIK, routers also just re-sych. The OS's are not capable of xx:xx:60 time.
For reading router logs this is fine in most cases which is all NTP is really
for. I don't think they simply step the time, I am pretty sure they do tweak
the freq. I could be wrong and I am NOT representing
In message: 13205c286662de4387d9af3ac30ef456afa8697...@embx01-wf.jnpr.net
Jonathan Natale jnat...@juniper.net writes:
: AFAIK, routers also just re-sych. The OS's are not capable of
: xx:xx:60 time. For reading router logs this is fine in most cases
: which is all NTP is really for.
M. Warner Losh wrote:
In message: 13205c286662de4387d9af3ac30ef456afa8697...@embx01-wf.jnpr.net
Jonathan Natale jnat...@juniper.net writes:
: AFAIK, routers also just re-sych. The OS's are not capable of
: xx:xx:60 time. For reading router logs this is fine in most cases
: which is
