Thanks Matthew
This just happened to me - the rollover went fine, but after a reboot came
back an hour behind.
I really appreciate you taking the time to explain this.
charles
On Wed, 26 Apr 2000, Matthew Saltzman wrote:
>
> And the last piece of the puzzle is: why didn't the update happen in
> the first place? And the answer is: your bios clock is probably set
> to local time. If /etc/sysconfig/clock contains "UTC=false", then
> the system assumes that the bios time is the correct local time and
> doesn't update for daylight savings. (Actually, the rollover will
> be handled correctly, but the next time you boot, you'll be an hour
> off again.)
>
> If this is a server (i.e., never boots anything but Linux), then
> configure your hardware clock to use Universal time ("UTC=true" in
> /etc/sysconfig/clock) and use
>
> hwclock --utc --systohc
>
> to set the clock. Then the system will correctly handle daylight time
> under all circumstances.
>
> The only reason to set your BIOS clock to local time is to support
> Windows, which is too brain-dead to understand Universal time. Real
> OS's always use UTC 8^).
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
