From: Ross Alexander (ralexan9@telusplanet.net)
Date: Thu Nov 14 2002 - 22:03:10 EST
On Thu, 14 Nov 2002, Lane, Debbie wrote:
> We did stop xntpd, as it was a suspect. The time server syncs HP and SUN
> boxes as well. The HP and SUN boxes did not have the date roll back
> problem.
How about the time server itself? Anyone have a look at it? BTW, is
IBM still shipping that ancient ntp 3.x stuff? I deep-sixed ours. The
4.x daemon man page notes:
[if] for some reason its time is more than 1000s from the server time,
ntpd assumes something must be terribly wrong and the only reliable
action is for the operator to intervene and set the clock by hand.
This causes ntpd to exit with a panic message to the system log. The
-g option overrides this check and the clock will be set to the server
time regardless of the chip time.
I'd have a dig through the logs and/or errpt, but this isn't the sort of
mistake ntp makes. Add the following into your /etc/ntp.conf and you'll
get an audit trail in /var/ntp:
statistics loopstats
statsdir /var/ntp/
filegen loopstats file loop type week link enable
regards,
Ross
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:20 EDT