Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Problem with registry date
Message-ID: <1990Aug6.193047.25822@terminator.cc.umich.edu>
Date: 6 Aug 90 19:30:47 GMT
References: <247@rangkom.MY>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 26

In article <247@rangkom.MY>, azman@rangkom.MY (Azman Bahrom) writes:

      1. the registry date is incorrect. It seems to have
         a "future" date. I realized this when I invoked rgy_admin :=

I keep my clocks in sync with ntpdate, available for anonymous ftp from
gw.ccie.utoronto.ca.  I run it from /etc/rc and a couple times a day from
cron.

You'll want to apply this patch (thanks to Bill Sommerfeld of Apollo).
There are others if you want to run xntpd (a more general and flexible way
of keeping your clocks synced).

*** ntpdate.c_o	Wed Apr 11 12:32:17 1990
--- ntpdate.c	Wed Apr 11 12:31:31 1990
***************
*** 1158,1163 ****
--- 1158,1165 ----
  	full_recvbufs = 0;
  	free_recvbufs = sys_numservers + 2;
  
+ 	setpgrp(0, getpid());
+ 
  	/*
  	 * Point SIGIO at service routine
  	 */