Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!usc!wupost!darwin.sura.net!sgiblab!rpal.rockwell.com!headwall.Stanford.EDU!kithrup.com!sef From: sef@kithrup.com (Sean Eric Fagan) Subject: Re: problems with clock? Organization: Kithrup Enterprises, Ltd. References: <C4pqxv.2Jq@kithrup.com> <C4q062.4Iv@veda.is> Message-ID: <C4q3B4.159@kithrup.com> Date: Tue, 30 Mar 1993 22:18:25 GMT Lines: 18 In article <C4q062.4Iv@veda.is> adam@veda.is (Adam David) writes: >I've yet to see a PC computer that does not continually lose time in the >BIOS clock. I'm not talking about the BIOS clock. I'm talking about the system clock, which is a combination of the hardware and software. In particular, 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.