What does your
/var/lib/ntp/drift
file contain? This is the offset the OS thinks it needs to maintain
correct time. If this is messed up, your OS time will be wrong, then
when you reboot, your hardware clock will be wrong as well. If this
number is really high, try removing the file and then restarting the
ntp service. It can take up to 15 minutes for the ntp service to re-
create this file, so don't get frustrated.
- Donald Tripp
[EMAIL PROTECTED]
----------------------------------------------
HPC Systems Administrator
High Performance Computing Center
University of Hawai'i at Hilo
200 W. Kawili Street
Hilo, Hawaii 96720
http://www.hpc.uhh.hawaii.edu
On Mar 2, 2007, at 12:13 PM, Paul Barrett wrote:
I originally installed CENTOS4.4 to try something new and was
having this
problem so I installed SL4.4 instead and still have the problem.
System is a IBM Workstation P4 with 512megs of ram and an nvidia
card. I
removed the Firewire card. SL Linux is installed in an almost
minimal ser
ver
install with vim and elinks as options.
The problem is that after setting the time with rsync and hwclock
within
about two ours they are drastically out of sync. The Hwclock has
the corr
ect
time but the systime by issuing 'date' is wrong. I have checked the
/etc/sysconfig/clock and it is set to utc=false and both the
hwclock an
d
systime will be correct after doing the rsync.
Additionally and most desturbing is the following. If I issue the date
command multiple times sometimes it returns a result that can be a few
seconds to a minute earlier than previously reported.
Is systime interupt driven and if so what irqs might have a conflict?
Any thoughts whatsoever could help.
Thanks in advance.
