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 Juniper here, just my thoughts. :-)
-----Original Message----- From: leapsecs-boun...@leapsecond.com [mailto:leapsecs-boun...@leapsecond.com] On Behalf Of leapsecs-requ...@leapsecond.com Sent: Friday, October 09, 2009 12:01 PM To: leapsecs@leapsecond.com Subject: LEAPSECS Digest, Vol 34, Issue 8 Send LEAPSECS mailing list submissions to leapsecs@leapsecond.com To subscribe or unsubscribe via the World Wide Web, visit http://six.pairlist.net/mailman/listinfo/leapsecs or, via email, send a message with subject or body 'help' to leapsecs-requ...@leapsecond.com You can reach the person managing the list at leapsecs-ow...@leapsecond.com When replying, please edit your Subject line so it is more specific than "Re: Contents of LEAPSECS digest..." Today's Topics: 1. Windows Time's "Great Leap Forward" (Matsakis, Demetrios) 2. Re: Windows Time's "Great Leap Forward" (Zefram) 3. Re: Windows Time's "Great Leap Forward" (Poul-Henning Kamp) ---------------------------------------------------------------------- Message: 1 Date: Fri, 9 Oct 2009 11:02:45 -0400 From: "Matsakis, Demetrios" <matsakis.demetr...@usno.navy.mil> Subject: [LEAPSECS] Windows Time's "Great Leap Forward" To: "Leap Second Discussion List" <leapsecs@leapsecond.com> Message-ID: <91772dec8a29c048a9bfbe32c49ceb724db...@echo.usno.navy.mil> Content-Type: text/plain; charset="us-ascii" 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 ------------------------------ Message: 2 Date: Fri, 9 Oct 2009 16:32:41 +0100 From: Zefram <zef...@fysh.org> Subject: Re: [LEAPSECS] Windows Time's "Great Leap Forward" To: Leap Second Discussion List <leapsecs@leapsecond.com> Message-ID: <20091009153241.gi20...@fysh.org> Content-Type: text/plain; charset=us-ascii 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. Although recent versions of Windows have come with an NTP client, as far as I can tell this client is incapable of performing anything resembling the NTP clock synchronisation algorithm. It merely steps the local clock to match the NTP server, each time it receives a reply from the server, and never steers the clock speed. It's typically configured to ask a server for the time once a *week*. This is not clock synchronisation as we know it, and one shouldn't be misled by the fact that it's capable of using a proper NTP server as its time source. -zefram ------------------------------ Message: 3 Date: Fri, 09 Oct 2009 15:51:08 +0000 From: "Poul-Henning Kamp" <p...@phk.freebsd.dk> Subject: Re: [LEAPSECS] Windows Time's "Great Leap Forward" To: Leap Second Discussion List <leapsecs@leapsecond.com> Message-ID: <12710.1255103...@critter.freebsd.dk> 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 since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ------------------------------ _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com http://six.pairlist.net/mailman/listinfo/leapsecs End of LEAPSECS Digest, Vol 34, Issue 8 *************************************** _______________________________________________ LEAPSECS mailing list LEAPSECS@leapsecond.com http://six.pairlist.net/mailman/listinfo/leapsecs
