Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!agate!ucbvax!GW1.AGS.BNL.GOV!roger
From: roger@GW1.AGS.BNL.GOV (Roger A. Katz)
Newsgroups: comp.sys.apollo
Subject: re: An easy way to keep your clocks synchronized
Message-ID: <9010191740.AA08224@gw1.ags.bnl.gov>
Date: 19 Oct 90 17:40:52 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14

ahhh, this might explain a problem i have been having. 

I use timed, and can report no problems with its use.  However I have
cron running on a node, and we have had an occurrance where cron started a
job two hours early. ie. job is to start at 17:00 started at 15:00, yet the
time of the node on which cron was running appeared correct.. useing /com/date
or lcnode or whatever to check the time.  Does cron use the boot-time clock?
is there a command to let me see what time the boot-time clock is?
Email: roger@gw1.ags.bnl.gov                Roger A. Katz
                                            AGS Software Controls Group
                                            Brookhaven National Laboratory
                                            Upton, N.Y. 11973-5000
                                            (516) 282-2732
I'm sure, I might be wrong, but I'm sure.