On Sun, Oct 28, 2001 at 06:52:55PM -0600, Nolan Darilek wrote: | Granted,, this problem only happens twice a year, but it's annoying | the hell out of me. :) | | My clock resets nicely during daylight savings, but the time doesn't | persist between reboots. I.e. this morning the time was correct, but | we suffered a brief power outage and the time was reset forward an | hour. Running rdate sets the time correctly, but I'd very much like to | resolve this issue, since my box's clock is practically my only | clock. This problem began when I installed my old drive into my new | system, so I'm suspecting something in the BIOS perhaps, but any more | definite pointers would be appreciated, since I've never been quite | bored enough to muck about in the BIOS. :)
Make a cron job that runs `/sbin/clock -w' every sunday at 4am and the problem will go away. The problem is that Linux reads the RTC at startup and then keeps track of the time internally. Since time is kept in epoch time, there's no `jump' at 2am at the switch -- that's all done in translating the time to `human' time. So the clock is right and stays right. ... until you reboot. Nothing has updated the RTC, so suddenly the time is an hour off. Windows will set the RTC for you the first time it boots after a DST change occurrs. Of course, this can cause the change to be made *twice* if Linux has already done it for you, so this can get confusing if you dual boot. :) -- Doug McLaren, [EMAIL PROTECTED] Well kiss my grits! --------------------------------------------------------------------------- Send administrative requests to [EMAIL PROTECTED]
