On Fri, 2007-09-07 at 17:44 +0100, Andy Green wrote: > Somebody in the thread at some point said: > > > P.S. Without NTP, system clock seem to run too fast on this machine... > > ntp has a "sanity check" limit, if the actual clock and the ntp time > differ by more than this (1000s? one thousand somethings IIRC) then it > just gives up. > > I also have a dual core AMD box where the clock is going nuts, much > faster than normal, and ntpd is powerless confronted with the temporal > madness. Make sure you have the IP addresses of your NTP servers in BOTH the /etc/ntp/ntpservers and /etc/ntp/step-tickers files. The first thing the startup script does is try to run "ntpdate" using the entries in the ntpservers file. That will drag your clock into sync with the servers by brute force, then ntpd can keep it synced. ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens@xxxxxxxxxxxx - - CDN Systems, Internap, Inc. http://www.internap.com - - - - It is better to have loved and lost. Cheaper, too! - ---------------------------------------------------------------------- -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
