Clock delay

[Juan L. Pastor]

On Sat, 2004-09-25 at 02:53, Stewart Nelson wrote:

> As one of the final shutdown steps, it sets the hardware clock from
> the system clock.  So even if the BIOS clock was not correct when you
> started, it should be when you are done.
> 
> Is NTP running?  If so, does the system have the correct time after it
> comes up?  After it has been running for a while?  If you forcibly
> kill the system, e.g. with the reset button, is the BIOS clock
> still wrong?  How much is the error?

To answer your questions:

- ntpd is not running, I don't have permanent connection to the
internet:

[root at kalimotxo root]# chkconfig --list | grep ntp
ntpd            0:off   1:off   2:off   3:off   4:off   5:off   6:off

- When I boot, the system has the correct time if I had set it just
before shutting it down.

- The clock has delays just with 2.6.8-1.521 kernel (not with Win2000 or
another kernel). The biggest delay it has is around 10 minutes, and it
takes this delay progressively during the first two hours. Afterward, no
more delay.

> If you won't be using NTP, check the BIOS time before booting,
> the system time right after it starts up, the system time just
> before shutdown, and the BIOS time after shutdown.  That should
> show whether the time is being lost at startup, during operation,
> or at shutdown.

Right after it starts up, the system time matches the BIOS time. Just
before shutdown, it has a delay, as I said like 10 min. as maximum, just
the same as the BIOS time, so the time is lost during operation, which
is logical as it doesn't happen with Win2000.

Juan

-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html