Mihai Ibanescu <[EMAIL PROTECTED]> wrote:
>On Wed, 26 Apr 2000, Chad Rismiller wrote:
>
>> On Wed, 26 Apr 2000, [EMAIL PROTECTED] wrote:
>>
>> > I just noticed my firewall server was never updated for daylight savings time.
>> > Is there a way to update the time w/o having to reboot the box? I remember
>> > reading somewhere that it was not a good idea to do this w/o a reboot.
It's not too bad to set the clock ahead without a reboot, but don't freak
when your screen blanker kicks in.
>> This is how I did it
>>
>> bash# date MMDDhhmm
>> bash# clock -w
>>
>> of course put in the actual month day hour minute
>
>To also update the BIOS clock (so that the next reboot to give you The
>Right Time(TM)):
>
>hwclock --systohc
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^).
Matthew Saltzman
Clemson University Math Sciences
[EMAIL PROTECTED]
http://www.math.clemson.edu/~mjs
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
