Re: FC 1: NTPD not keeping time correctly

akast82_at_coatimundi.net
Date: 09/08/04

  • Next message: William Hooper: "Re: FC 1: NTPD not keeping time correctly" 
    Date: Wed, 8 Sep 2004 12:36:32 -0700
To: fedora-list@redhat.com

    On Wed, 8 Sep 2004, Matthew Miller wrote:

    > On Wed, Sep 08, 2004 at 11:56:10AM -0400, Clint Harshaw wrote:
    > > I have tried each of the three redhat clocks that are listed in the
    > > Adjust Date/Time gui, and have a check in Enable Network Time Protocol.
    > > What am I missing that is preventing the clock to properly sync up and
    > > maintain the correct time?
    >
    > Are you running a firewall? Have you used the system-config-securitylevel
    > (or lokkit) tools to change its settings, but not restarted NTP?

    In addition to all these critical points about ntp configuration, firewall
    configuration, and NTP server relationships, I would like to point out that
    NTP also fails to work with exceptionally inaccurate system clocks.

    I encountered this problem recently with a Dell Latitude 810 laptop. The
    verbose ntp documentation (installed with Fedora) explains that ntpd can't
    correct for clock frequency errors greater than 500 parts per million. My
    system clock was of by about one part in 100, so the clock was never right.

    If none of the other suggestions work out, you might try learning to read the
    output from ntpq and see if the daemon is unable to synchronize. See
    file:///usr/share/doc/ntp-4.2.0/debug.html. I fixed my problem by installing
    the adjtimex package, and then using /sbin/adjtimex to alter the kernel's
    "tick" value until ntpd could lock on.

    Anton 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: William Hooper: "Re: FC 1: NTPD not keeping time correctly"

    Relevant Pages

    • Re: Clock drift problems
      ... the real-time clock has gotten 7 hours slow. ... I can understand that, but things like NTP ... Maximum drift rate for ntpd is 500ppm or something tiny like that. ... on x86 ATX motherboard linux boxes that are doing heavy I/O ...
      (comp.os.linux.misc)
    • Re: [PATCH/RFC 10/10] example of simple continuous gettimeofday
      ... Uses NTP to modify the clock frequency value rather then just ... > adjustment, which should be applied every f cycles. ... Your design seems to suggest keeping an NTP calculated reference time ...
      (Linux-Kernel)
    • Re: ntp discipline of local time?
      ... Principles and Precision Time Synchronization briefings on the NTP project page are old but applicable. ... The details you are asking for are carefully explained in the NTPv4 spec. ... like the clock state machine and poll-adjust algorithm continue in the daemon. ... factor from CPU cycles to time) and get rid of the offset. ...
      (comp.protocols.time.ntp)
    • Re: [PATCH/RFC 10/10] example of simple continuous gettimeofday
      ... >> The basic idea behind this is that ntp defines the frequency of the ... >> adjustment, which should be applied every f cycles. ... >> which allows for a very stable clock. ... >> resolution is still well within the practical limits of the clock. ...
      (Linux-Kernel)
    • Re: ntp discipline of local time?
      ... Principles and Precision Time Synchronization briefings on the NTP ... does two things-- set the system clock frequency (ie adjust the conversion ... factor from CPU cycles to time) and get rid of the offset. ... frequency and phase errors. ...
      (comp.protocols.time.ntp)