Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!sun-barr!apple!olivea!jerry
From: jerry@olivey.ATC.Olivetti.Com (Jerry Aguirre)
Newsgroups: comp.protocols.time.ntp
Subject: Re: Running NTP at Verdix.Com
Summary: uunet.uu.net is not a good NTP peer
Message-ID: <50558@olivea.atc.olivetti.com>
Date: 27 Mar 91 06:14:03 GMT
References: <9103192021.AA17181@Verdix.COM> <9103192032.AA09380@sayshell.umd.edu>
Sender: news@olivea.atc.olivetti.com
Distribution: inet
Organization: Olivetti ATC; Cupertino, CA
Lines: 14

In article <9103192032.AA09380@sayshell.umd.edu> louie@SAYSHELL.UMD.EDU ("Louis A. Mamakos") writes:
>
>Sounds reasonable to me.  Since UUNET is synchronized to UMD1
>directly, you might just want to synchronize with them only and not
>increase the already heavy load on UMD1 any further.

I have monitored uunet.uu.net for quite a while.  It does not keep good
time being usually some large fraction of a second off.  Its NTP daemon
seems to know this but be unable to correct the local time to less than
1 second accuracy.  I assume this represents some problem with the
hardware or kernel.  The other systems at uunet don't seem to run NTP.

On the other hand for most people who are happy with the right second it
is probably good enough.