Path: utzoo!attcan!uunet!mailrus!tut.cis.ohio-state.edu!ucbvax!UMIX.CC.UMICH.EDU!krowitz%richter
From: krowitz%richter@UMIX.CC.UMICH.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  ncs-clocks skew warning
Message-ID: <9003191745.AA03515@richter.mit.edu>
Date: 19 Mar 90 17:45:44 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19

The global loation brokers use the time/date when updating each other
when NCS servers startup or shutdown. If the clocks on the machines
running GLBD are more than 5 or 10 minutes out of sync, the location
broker can not update each other because events which are registered on one
machine can appear to be occuring in the *future* on the other machine.
Under SR10.2 (and possbily SR10.1) you can use the Unix "date" command
reset the machine's time and date to the correct value without having to
shutdown the machine to run EX CALENDAR. There is also a new daemon called
"timed" which is supposed to keep machines from having their clocks drift
with repect to one another. I haven't tried it out yet, so I can't say
whether is works or not. 


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)