Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!van-bc!ubc-cs!pphillip From: pphillip@cs.ubc.ca (Peter Phillips) Newsgroups: comp.sys.apollo Subject: Re: Problem with registry date Message-ID: <9032@ubc-cs.UUCP> Date: 7 Aug 90 03:31:25 GMT References: <247@rangkom.MY> <1990Aug6.193047.25822@terminator.cc.umich.edu> Sender: news@cs.ubc.ca Organization: University of British Columbia, Vancouver, B.C., Canada Lines: 25 In article <1990Aug6.193047.25822@terminator.cc.umich.edu> rees@citi.umich.edu (Jim Rees) writes: >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). [ patch omitted ] This sounds great. However, is it really safe to be adjusting the system clock time while the machine is running? The clock is used a seed for assigning identifiers (UIDs in Domain/OS parlance (no UNIX UIDs)) to objects. If the clock is set back, two identifiers can coincide causing disaster. I know ntp implementations use adjtime(2) which shouldn't move the clock backward at all but the manual page for adjtime(2) in Domain/OS is not clear if the use of adjtime is safe. So, does anyone out there with "kernel" knowledge know if running NTP-related time synchronization software is safe/reliable on Apollos? -- Peter Phillips, UBC Computer Science| Listen: | Billy Pilgrim has come unstuck in time.