Path: utzoo!attcan!uunet!decwrl!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: <9010291419.AA05630@pan.ssec.honeywell.com> Date: 29 Oct 90 14:19:04 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 43 Hi -- I'm cross-posting this to the apollo list and also to the Mentor one. (Sorry if, like me, you're on both.) It seems relevent. > <> > from: umix.cc.umich.edu!apollo-request > subj: re: An easy way to keep your clocks synchronized > > > > 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 am running the timed daemon on Mentor 7.0 idea-stations and > board-stations without any problems with Mentor programs whatsoever. I believe that you've just been exceedingly lucky. I had the same situation when I started using 'timed'. Because I had no problems with it at first, I figured that I was safe. It wasn't until after I had set up timed on all the 10.2 nodes (we had mixed 9.7, 10.1, and 10.2 at the time), and waited a day or two, that everybody started complaining about Mentor tools refusing to start. If your calendars are close, and the clocks aren't drifting too far relative to each other, you'll appear to be safe. However, Mentor stated in CSB #79 (July 89) on page 20 that they check, as part of their authorization-scheme, whether you've changed the date since boot-time. Now, whether this is stupid is not under debate. :-) However, as long as they _do_ do this check, I would not advise running 'timed', and in fact would advise _against_ it. BTW: Does anyone at Mentor want to comment on whether the 10.3 version of Mentor 7.0 (7-UP) still has this bug/feature? If I hear nothing, I guess I'll play guinea-pig with a node and find out the hard way.... 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)