Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!HPSDLZ.SDD.HP.COM!ken
From: ken@HPSDLZ.SDD.HP.COM (Ken Stone)
Newsgroups: comp.protocols.time.ntp
Subject: Re: How widely deployed is NTP?
Message-ID: <9103090415.AA24449@hpsdlz.sdd.hp.com>
Date: 9 Mar 91 04:15:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 16


> All of our systems run ntpdate very hour (if their clocks drift some)
> or every three hours if they don't drift much.  It keeps them all
> withing a second quite nicely.  That seems close enough for what
> we do, and of course we use ntpdate at boot time to set the clock.

I ran some tests here and found that an xntpd running as a broadcast 
client took less umph than running ntpdate or rtime or whatever out 
of cron.  We found that we had large cad program users that could tell 
us when ntpdate ran out of cron consistantly even with us varying the 
times whereas a xntpd presented a much lighter and consistant load that 
no one noticed.  This is on medium sized workstations.

Just a thought ...

  -- Ken