Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!caen!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: An easy way to keep your clocks synchronized
Message-ID: <4d6ef002.1bc5b@pisa.ifs.umich.edu>
Date: 16 Oct 90 14:44:46 GMT
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 15

You need to keep your node clocks synchronized to within 5 minutes of each
other if you want NCS based services like the registry to work right.  Nodes
can easily drift 5 minutes apart in a few weeks, so you need some way to
keep them synchronized.

The best way is with xntp.  It requires that you have TCP and needs some
configuration.

If you don't want to go to that much trouble, I have a program that simply
sets one node's clock from another node on the same Domain network.  It
doesn't require TCP or any configuration other than the name of the node to
acquire the clock from.

You can get it by anonymous ftp from dabo.ifs.umich.edu, in 'date.tar.Z'.
I haven't included the source because it uses unreleased calls.