Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mstar!mstar.morningstar.com!bob From: bob@MorningStar.Com (Bob Sutterfield) Newsgroups: comp.protocols.time.ntp Subject: Re: Time server for HP 9000/3xx?? Message-ID: Date: 5 Jan 91 05:57:07 GMT References: <370@esl.ESL.COM> <4f01944d.1bc5b@pisa.ifs.umich.edu> Sender: usenet@MorningStar.COM (USENET Administrator) Reply-To: bob@MorningStar.Com (Bob Sutterfield) Distribution: na Organization: Morning Star Technologies Lines: 18 In-Reply-To: rees@pisa.ifs.umich.edu's message of 4 Jan 91 16:15:42 GMT In article <4f01944d.1bc5b@pisa.ifs.umich.edu> rees@pisa.ifs.umich.edu (Jim Rees) writes: In article <370@esl.ESL.COM>, jsd@esl.ESL.COM (Jeff Dalton) writes: ...xntp for the Sun ... seems to be a lot more than I need... all the nodes just need to be within a second or so. What I do here is run xntpd on a few select machines, then the rest of them sync off those by using ntpdate run from cron every few hours. The NTP protocol and the UNIX daemon's clock adjustment strategy are very economically designed, to accomplish the task with a minimum of intrusion. The memory and CPU cost of running xntpd on a workstation is remarkably low, since it is fairly small and only schedules itself when it knows it will really be needed. The overhead of a local networkful of workstations chiming with each other is also remarkably low, and will disappear into the background noise on your wire. Don't be afraid to run the daemon everywhere.