Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: re: An easy way to keep your clocks synchronized
Message-ID: <4d7f007e.1bc5b@pisa.ifs.umich.edu>
Date: 19 Oct 90 19:30:38 GMT
References: <9010191740.AA08224@gw1.ags.bnl.gov>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 21

In article <9010191740.AA08224@gw1.ags.bnl.gov>, roger@GW1.AGS.BNL.GOV (Roger A. Katz) writes:
  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..

Two hours is a long time.  I would suspect something more like you have the
time zone set wrong.  Or I suppose cron might get confused if the time was
way off when you booted the node.  I usually try to get the time set within
ten minutes or so using offline "calendar," then fine-tune it with something
like xntp after booting.

  Does cron use the boot-time clock?

"cron" is just an ordinary Unix program and uses the same clock that "date"
uses.

  is there a command to let me see what time the boot-time clock is?

Not that I know of, but you could write one.  Use uid_$gen() to generate a
uid, and extract the time out of the top 36 bits.