Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!ucbvax!ERG.SRI.COM!davy
From: davy@ERG.SRI.COM
Newsgroups: comp.protocols.time.ntp
Subject: Re: Not a Lord a-leaping
Message-ID: <9101011832.AA03620@intrepid.erg.sri.com>
Date: 1 Jan 91 18:32:58 GMT
References: <9012312226.aa10954@huey.udel.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 30


     From:  Mills@udel.edu
     Date:      Mon, 31 Dec 90 22:26:09 EST
     Subject:   Not a Lord a-leaping

     Well, the fuzzballs got it right this time. Now, about the
     others. Don't ask.
     
     Dave

I had one machine here complain about it three times, but nothing bad happened,
i.e. no time warps:

Dec 31 21:57:19 san ntpd[127]: Clock is too far off -31536000.142805 sec. [132.249.16.1]
Dec 31 21:58:23 san ntpd[127]: Clock is too far off -31536000.142805 sec. [132.249.16.1]
Dec 31 21:59:27 san ntpd[127]: Clock is too far off -31536000.142805 sec. [132.249.16.1]

The "Dec 31 ..." times are in PST.  132.249.16.1 is fuzz.sdsc.edu.

The leap didn't seem to bother ntp3.4 and my WWVB clock... although the
dispersion has jumped way up:

   (rem)  Address   (lcl)      Strat Poll Reach    Delay   Offset    Disp
==========================================================================
*0.0.0.0         wildcard          1   64  377       1.0    -64.0   7522.0

It usually runs down at something less than 10.0.  I'll have to wait and
see if it stabilizes again in the next 24 hours or so.

--Dave