[wplug] NTP and bad time sources

[John Strange]

Hmm

By default I've always seen ntpd refuse to set the time if the
difference is greater than 1 hour, hence the reason that you run ntpdate
before you set it with ntpd.

More than likely your BIOS date is off, check with hwclock and set it
correctly.  The best way to setup your ntp stuff is to setup one/two
ntpd servers internally that go outside to sync, then set the rest of
your machines to sync off those.  Old hardware that you have laying
around works great for it.

- John

On Fri, 2003-05-23 at 11:01, Bob Schmertz wrote:
> Any NPT experts here?
> 
> I've been reading the HTML documentation for NTP, and I wonder if someone could clarify something for me. It makes mention of ntpd exiting if the time differential between the host and source is greater than the threshold, but it's not clear whether it claims to exit only if this discrepancy is seen on startup, or whether it will do this at any time. In my experience, on Linux, NTP will adjust the system time to whatever wacko time the NTP source decides to spit out, as long as the time seemed reasonable when ntpd started up in Linux. I'm seeing my source time get reset to wildly different times (usually Jan 1, 2003) for unexplained reasons, and I'd like for my Linux boxes not to swallow these changes, but to bail out.
> 
> If the behavior I have observed is the actual default behavior of NTP, does anyone know of any way of making it do something more reasonable on a wild reset of the source (hopefully without modifying the source code :-))?
> 
> Thanks,
> Bob
> 
> 
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug