Xref: utzoo comp.unix.sysv386:6872 comp.dcom.lans:7739
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!mintaka!spdcc!rbraun
From: rbraun@spdcc.COM (Rich Braun)
Newsgroups: comp.unix.sysv386,comp.dcom.lans
Subject: Network Time Server
Message-ID: <7274@spdcc.SPDCC.COM>
Date: 11 Apr 91 19:43:57 GMT
Followup-To: comp.unix.sysv386
Organization: Kronos Inc., Waltham, Mass.
Lines: 12

I recently brought up timed on a couple of SCO Unix systems and an RS-6000,
hoping to have a reliable, synchronized time source on my TCP/IP LAN.
Instead, I have a bunch of synchronized systems which lose about a
minute per day.  The SCO documentation doesn't say anything about how
one sets up a reference time source; timed only serves the purpose of
synchronization, and there's no way of telling it which system is "the"
reference source.

How do I solve this problem?  I'm working for a company whose business
is selling clocks, so needless to say, inaccurate clocks are particularly
annoying to me ;=)

-rich