Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!jhunix!andy
From: andy@jhunix.HCF.JHU.EDU (Andy S Poling)
Newsgroups: comp.protocols.time.ntp
Subject: ntpd says lost NTP peer right after synching...
Message-ID: <7963@jhunix.HCF.JHU.EDU>
Date: 11 Apr 91 22:49:15 GMT
Organization: The Johns Hopkins University - HCF
Lines: 23

I'm running the ntpd code from louie.udel.edu on two Ultrix boxes and a SysV
port of the same code on a box running SysV rel 3.1.5 and I'm seeing the
same thing happen on all three...

Whenever they choose a server to which to synchronize, they then seem to
lose all of the data about that server causing an "NTP peer lost" message
and a constant swapping of the available, sane, servers.

This just doesn't seem quite right to me since it causes ntpd to query it's
favorite two or three servers every 64 seconds most of the time, rather than
sliding to a 1024 second interval (which seems to me like the thing to do).
I admit that I haven't studied the NTP spec in detail...

Am I missing something?  Being stupid?  Is there any reason why I shouldn't
modify the code to prevent this behavior?

Thanx,
-Andy
--
Andy Poling                              Internet: andy@gollum.hcf.jhu.edu
UNIX Systems Programmer                  Bitnet: ANDY@JHUNIX
Homewood Academic Computing              Voice: (301)338-8096    
Johns Hopkins University                 UUCP: uunet!mimsy!aplcen!jhunix!andy