Re: clock running fast

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 12/30/04

  • Next message: Federico Galvez-Durand Besnard: "Re: clock running fast"
    Date: Thu, 30 Dec 2004 12:13:18 -0800
    To: Javier Henderson <Javier@kjsl.com>
    
    
    

    On Thu, Dec 30, 2004 at 11:37:04AM -0800, Javier Henderson wrote:
    > > > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \
    > > > - -f /var/db/ntpd.drift
    > >
    > > It's generally recommended that you never trust your own clock since
    > > it's completely crap as time sources go. It's also recommended that you
    > > use at least 5 time sources to avoid problems with bad clocks.
    >
    > But isn't that what the drift file is for, to improve the accuracy of
    > the local clock during those times when the configured NTP servers aren't
    > available?

    Yes, but it can only do so much. The clock crystals in your average PC
    are OK as clocks, but much better as thermometers so the drift
    calculations are only approximate.

    -- Brooks

    -- 
    Any statement of the form "X is the one, true Y" is FALSE.
    PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
    
    



  • Next message: Federico Galvez-Durand Besnard: "Re: clock running fast"

    Relevant Pages

    • Re: suggestion
      ... Possible time sources for the box are: ... NTP server (optional and configurable: ... local GPS connected to serial line (an alternative to NTP: ... it instead of any sort of cronjob calling ntpdate to step the clock. ...
      (comp.protocols.time.ntp)
    • Re: Two time sources with offset => fails to synchronize
      ... It seems that the Radio clock has 50ms offset compared to the GPS ... time sources is the worst configuration you can have. ... have configured a local GPS clock and 3 external servers then the external ...
      (comp.protocols.time.ntp)
    • Re: clock running fast
      ... > It's generally recommended that you never trust your own clock since ... > it's completely crap as time sources go. ... > use at least 5 time sources to avoid problems with bad clocks. ... the local clock during those times when the configured NTP servers aren't ...
      (freebsd-stable)
    • Re: clock running fast
      ... It's generally recommended that you never trust your own clock since ... use at least 5 time sources to avoid problems with bad clocks. ... >>ntpdate, and my ntpq queries look fine, yet the clock persists in running ... >>David Talkington ...
      (freebsd-stable)
    • Re: [SLE] Updating the system clock
      ... Maybe I'm misunderstanding the udel description of ntpd, ... each such occasion the hardware clock is set to the time gotten from the ... external servers, and the drift file is updated. ... if that's what happens then the drift file is useless. ...
      (SuSE)