Article: 11892 of comp.protocols.time.ntp From: Yan Seiner Newsgroups: comp.protocols.time.ntp Subject: Re: xntp on linux Date: Fri, 05 May 2000 09:29:41 -0400 Organization: http://extra.newsguy.com Lines: 53 Message-ID: <3912CCC5.547B9F4B@cardinalengineering.com> References: <390F580F.7621239C@anim.dreamworks.com> <8eoslc$9k3$1@hdxl22.telecom.ptt.nl> Reply-To: yan@cardinalengineering.com NNTP-Posting-Host: p-848.newsdawg.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en Path: news1.meer.net!news3.best.com!news1.best.com!nntp.primenet.com!nntp.gctr.net!nntp.giganews.com!cyclone-sf.pbi.net!207.211.168.17!pln-w!spln!extra.newsguy.com!newsp.newsguy.com!enews3 Xref: news1.meer.net comp.protocols.time.ntp:11892 Here's a nifty thing I cribbed from the FAQ and stuck in the crontab: 0 6 * * 1,3,5 if `newer /etc/ntp/drift /etc/ntp/tick` ; then echo "scale=7; `tickadj` ; drift=`cat /etc/ntp/drift`; t=tick*(1+(drift)/2^20)+0.5; scale=0;t/1" | bc > /etc/ntp/tick ; tickadj `cat /etc/ntp/tick` ; fi Add this, and also touch /etc/ntp/tick . Assuming, of course, that your drift file is in /etc/ntp. Adjust as necessary. You only need to run this for a short while (a week or so) and your tickadj should stabilize. Every time the tickadj changes, you may lose synchronization, so be aware of that. YMMV. --Yan Johan Swenker wrote: > > In article <390F580F.7621239C@anim.dreamworks.com>, ampl@anim.dreamworks.com > says... > > > >Hello, > > I am getting the following in /var/log/messages. I have replaced the > >ip addressess by X1, X2, X3. This does not seem right. My network is > >mostly SGIs, starting to integrate linux into the network. The SGIs are > >also running xntp, but I do not see large adjustments like the .29 > >second adjustment on the SGIs. Below is the ntp.conf file. Do I have to > >add more to the ntp.conf file? > > > >May 2 15:05:09 localhost xntpd[483]: synchronized to X1, stratum=2 > >May 2 15:08:55 localhost xntpd[483]: synchronized to X2, stratum=2 > >May 2 15:09:03 localhost xntpd[483]: synchronized to X3, stratum=2 > >May 2 15:19:15 localhost xntpd[483]: time reset (step) 0.291883 s > It is in the FAQ: > you should adjust the value of tick. By increasing tick by 1, your clock will > gain 1 microsecond per clock tick. First compute how much you have to gain in > an hour; next compute how much you have to gain in 1 clock tick (10 msec on > Intel Linux); finally adjust tick accordingly using tickadj or adjtimex. > > >May 2 15:19:15 localhost xntpd[483]: synchronisation lost > >May 2 15:24:08 localhost xntpd[483]: synchronized to X2, stratum=2 > > Succes, Johan -- Think different ride a recumbent use Linux.