On Tue, 2005-10-04 at 12:27 -0400, Michael W Cocke wrote:
You don't mention your hardware details but there was a design decision made back in the stone age that causes the hardware clock to drop a bit under heavy disk IO (like a mail server with possible insufficient cache ram). The technical explanation of the problem is "Critical interrupt masking during disk IO". I don't know if the linux system clock driver compensates for that properly or not. My usual practice (since DOS days, as a matter of fact) has been to have a NIST clock update (like ntpdate) run every 12 or 24 hours.
Mike-
Or vi /etc/ntp.conf and under "Outside source of synchronized time" add in: server us.pool.ntp.org server us.pool.ntp.org server us.pool.ntp.org Which will get 3 different server IP's. Then do a "chkconfig xntpd on". No more time issue. Brad Dameron SeaTab Software www.seatab.com