Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!wupost!uunet!enterpoop.mit.edu!ai-lab!hal.gnu.ai.mit.edu!not-for-mail From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum) Newsgroups: comp.os.386bsd.bugs Subject: Re: problems with clock? Date: 30 Mar 1993 23:12:04 -0500 Organization: dis Lines: 26 Message-ID: <1pb5mk$12lv@hal.gnu.ai.mit.edu> References: <C4pqxv.2Jq@kithrup.com> <C4q062.4Iv@veda.is> <C4q3B4.159@kithrup.com> NNTP-Posting-Host: hal.ai.mit.edu In article <C4q3B4.159@kithrup.com> sef@kithrup.com (Sean Eric Fagan) writes: } } I'm talking about doing something like: } } ntp -s <somereliablesite> } } and then, later, doing } } ntp <thatsamesite> } } and having a discrepency between 4 and 212 seconds. Once it starts } to lose track, it starts to increase wildly -- I've seen it go from a } difference of about 1.12 seconds to 179 seconds in about 20 minutes. Huh? This sounds like a bug in your implementation of `ntp'. I use `xntp' version 3, which you can get from: alpha.gnu.ai.mit.edu:/386bsd/README xntp3.tar.z -- \ / Charles Hannum, mycroft@ai.mit.edu /\ \ PGP public key available on request. MIME, AMS, NextMail accepted. Scheme White heterosexual atheist male (WHAM) pride!