Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson
From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson)
Newsgroups: comp.sys.apollo
Subject: re: An easy way to keep your clocks synchronized
Message-ID: <9010191430.AA02152@pan.ssec.honeywell.com>
Date: 19 Oct 90 14:30:23 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24


> Are there any compelling reasons for not using the timed daemon to
> synchronize clocks? 
Only if you run Mentor software.  As soon as the time gets changed, Mentor
(version 7.0) will no longer start programs.  "It's not a bug, it's a FEATURE!"

> I did that, and while possibly I have placed a
> time-bomb into the uid-generation mechanism, it has not showed up
> after several weeks of operation.
I don't believe there's a time-bomb.  Unless I'm horribly off-base, Apollo
keeps (the equivalent of) two clocks.  There's the base time, which is
set at boot-time (actually, system shutdown?) that ticks merrily away, and
there's the offset that timed (or '/bin/date' as root) have set up.  Until
you reboot, I don't believe that offset is used for creating UIDs.
(Incidentally, confirmation or refutation of the above by an 'in-the-know'
HP/Apollo person would be appreciated.)

John Thompson (jt)
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

As ever, my opinions do not necessarily agree with Honeywell's or reality's.
(Honeywell's do not necessarily agree with mine or reality's, either)