John Andersen a écrit :
On Saturday 16 December 2006 02:42, Daniel Bauer wrote:
In my experiences ntp deamon adjust the time only if the difference is less
than 3600 seconds. You can see in /var/log/ntp if there is a message like I
had it:
"time correction of -3600 seconds exceeds sanity limit (1000); set clock
manually to the correct UTC time."
That's what command line switch -g is for.
RTFM:
Most operating systems and hardware of today incorporate a
time-of-year (TOY) chip to maintain the time during
periods when the power is off. When the machine is booted,
the chip is used to initialize the operating system time.
After the machine has synchronized to a NTP server, the
operating system corrects the chip from time to time. In
case there is no TOY chip or 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. However, and to protect
against broken hardware, such as when the CMOS battery
fails or the clock counter becomes defective, once
the clock has been set, an error greater than 1000s will
cause ntpd to exit anyway.
jdd
--
http://www.dodin.net
http://dodin.org/mediawiki/index.php/GPS_Lowrance_GO
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
