Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mcsun!ukc!mucs!els!dente
From: dente@els.uucp (Colin Dente)
Newsgroups: comp.sys.apollo
Subject: Re: ncs-clocks skew warning
Message-ID: <1097@m1.cs.man.ac.uk>
Date: 19 Mar 90 17:31:36 GMT
References: <9003191219.AA12175@apo.esiee.fr>
Sender: news@cs.man.ac.uk
Reply-To: dente@els.ee.man.ac.uk (Colin Dente)
Organization: University of Manchester, UK
Lines: 27

In article <9003191219.AA12175@apo.esiee.fr> bonnetf@apo.esiee.fr (bonnet-franck) writes:
>hello,
>I have a warning problem with the clocks of the 2 glbd daemons on my system.
>The message looks like the following :
>>drm_admin: lrep -clocks
>	dds://tpd1            	1990/03/19.11:48	*** clock skew warning
>	dds://sig2            	1990/03/19.11:41	*** clock skew warning
>
>What does it EXACTLY means

What it means is that the clocks on the two systems are set to
different times.  This will not usually cause problems, but could
result in data being lost from as when glbds synchronize their
databases the most recent entry from either database is used, and,
with the clocks skewed, it would be possible to have the most
up-to-date entry not have the most recent time stamp.

The way round this is to reset the system clocks by means of the stand
alone utility CALENDAR - i.e. EX CALENDAR from the MD.

Colin


 Colin Dente                      | JANET: dente@uk.ac.man.ee.els
 Dept. of Electrical Engineering  | ARPA:  dente@els.ee.man.ac.uk 
 University of Manchester         | UUCP:  ...!mcvax!ukc!man.ee.els!dente 
 England                          | These might work now, but then again...