Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!rphroy!rrichter
From: rrichter@link.ph.gmr.com (Roy Richter)
Newsgroups: comp.protocols.time.ntp
Subject: Re: XNTPD problems on SPARC w/ SunOS 4.1.1
Message-ID: <55611@rphroy.UUCP>
Date: 10 Jun 91 14:34:33 GMT
References: <90C443480021E50F@ecl.psu.edu>
Sender: news@rphroy.UUCP
Reply-To: rrichter@link.ph.gmr.com (Roy Richter)
Distribution: inet
Organization: GM Research, Warren, Mi
Lines: 18
Nntp-Posting-Host: link.ph.gmr.com

In article <90C443480021E50F@ecl.psu.edu>, JDB@ECLA.PSU.EDU ("John D. Balogh, PSU OTC, 814.863.1252") writes:
|> Back on Nov. 12, 1990, Dave quoted Van Jacobson on the following:
|> "Sun has incorporated the System V timekeeping code in 4.x and that
|> this code is broke to max."

I think there are several groups of people syncing clocks who are distinguished
by their desired level of accuracy.  Comments like the above are from an
extremum group, who desire sub-millisecond accuracy.  This group is needed to
further clock research, but I personally don't think such accuracy is needed
for daily operations.  I'm willing to be proved wrong, however.

Here we run 4.1.1 and seem to be keeping time to the 10-20 millisecond level
with little problem.  If you are happy with this accuracy, do it and don't
worry.  If you are not happy, and you know who you are, worry.

--
Roy Richter                  Internet: rrichter@ph.gmr.com
Physics Dept, GM Research    UUCP:     {umich,cfctech}!rphroy!rrichter