Article View: comp.protocols.time.ntp
Article #739Re: ntpd says lost NTP peer right after synching...
From: "Louis A. Mamakos"
Date: Fri, 12 Apr 1991 22:12
Date: Fri, 12 Apr 1991 22:12
9 lines
957 bytes
957 bytes
It sounds like what is happening is that when ntpd initially selects a host, it had to reset the local clock rather then slew it because it was too far off. Whenever the local clock is reset, all of the offset/delay samples in the filters are flushed, and we start all over again. It then reselects a peer, but the selected clock is too far off again. Could it be that your network paths are exceptionally "noisy" or that you computers are keeping really crummy time? louie
Technical Details
Message-ID:
<9104122212.AA02914@sayshell.umd.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!bionet!agate!ucbvax!SAYSHELL.UMD.EDU!louieReferences:
<7963@jhunix.HCF.JHU.EDU>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!bionet!agate!ucbvax!SAYSHELL.UMD.EDU!louie
From: louie@SAYSHELL.UMD.EDU ("Louis A. Mamakos")
Newsgroups: comp.protocols.time.ntp
Subject: Re: ntpd says lost NTP peer right after synching...
Message-ID: <9104122212.AA02914@sayshell.umd.edu>
Date: 12 Apr 91 22:12:00 GMT
References: <7963@jhunix.HCF.JHU.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 9