On Monday, 23.10.2006 at 09:02 -0500, Kent West wrote: > Ed Curtis wrote: > > It's not a dual-boot. I'm not sure but I think the bios date/time had > > something to do with it because I haven't had a problem with it since > > resetting it and updateing with ntpdate. > > > > I'm unsure about modern hardware, but older machines often suffered from > clock-drift, and could be particularly affected by system load and/or > weak/dying CMOS batteries. > > I'm unsure if ntpdate sets the hardware clock; if it does, I would doubt > this explanation. If not, I would suspect this as the problem. > > As far as some of your apps exhibiting strange behaviour, I can only > assume they're clock-sensitive in some way.
Yes: Apache is - I believe - rather sensitive to clock reversals. That is the symptom of the more general clock problem. If installed correctly and able to do so, Debian will synchronise the hardware clock to the current system time (see /etc/init.d/../init.d/hwclock.sh). Set your hardware clock to UTC and make sure ntpdate runs at boot-up (assuming you can see the Internet at boot-up) and all should be well. If not, then something is stopping your clock synchronising. Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
