[NTLUG:Discuss] Strange clock behaviour

[Stephen Klein]

Jim Goode wrote:
> Anytime I've had a problem with a system clock... it turned out to be that
> the battery on the motherboard needed to be replaced. Typically replacements
> on the boards I've had required a CR2032 battery. You might want to check
> that out.
> 
> Jim
> 
> -----Original Message-----
> From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org]On Behalf
> Of Rev. wRy
> Sent: Friday, September 22, 2006 1:32 PM
> To: NTLUG Discussion List
> Subject: [NTLUG:Discuss] Strange clock behaviour
> 
> 
> All -
> 
> I'm having a problem that I've never encountered before - the clock on
> my system will stop or run backwards.
> 
> example:
> 
> [root at fatboy ~]# date
> Fri Sep 22 13:12:51 CDT 2006
> [root at fatboy ~]# date
> Fri Sep 22 13:12:53 CDT 2006
> [root at fatboy ~]# date
> Fri Sep 22 13:12:50 CDT 2006
> [root at fatboy ~]# cd
> [root at fatboy ~]# date
> Fri Sep 22 13:12:49 CDT 2006
> [root at fatboy ~]# date
> Fri Sep 22 13:12:50 CDT 2006
> [root at fatboy ~]# date
> Fri Sep 22 13:12:52 CDT 2006
> [root at fatboy ~]# date
> Fri Sep 22 13:12:53 CDT 2006
> 
> CentOS 4.4 2.6.9-42.0.2 ntpd is not running.
> 
> Any ideas?
> 
> RW
> 
> 
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.12.5/450 - Release Date: 9/18/2006
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.12.5/450 - Release Date: 9/18/2006
> 
> 
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
> 
> 


The date command only checks the system time, which is separate from 
your realtime clock on the motherboard.  The realtime clock can be 
checked using hwclock.  If your BIOS provides it, you might check your 
battery voltage in the hardware monitor, but I don't think that's the 
case in this situation.

You also might check to see if adjtimex is being run from cron.

Other than that, I'm not sure, it is an odd problem.

Hope this  helps,
Stephen