At 09:52 AM 12/15/99 -0500, J. Scott Kasten wrote:
>Well, there's a couple things here to keep in mind. First, when you
>set the system time, all you're doing is setting the SOFTWARE clock,
>which of course gets it's time initially from the hardware on boot.
>You can set the hardware clock from the SOFTWARE clock. "man hwclock"
>However, there are known timezone issues, and you may or may not have
>the system configured to have the hardware clock set to GMT.
>
>I for example, use the hw clock set to GMT, and the software clock
>uses my timezone offset to display the real time. However, if I use
>the hwclock routine to try and set the hw clock, it forgets to apply
>the offset and sets it wrong. It seems the right way to set the
>hw clock is to actually go through BIOS when you do a reboot. That
>will guarantee that you avoid these zone issues and the known bugs.
>Thus I just take the real time, account for daylight savings, and
>apply my zone offset to get the GMT time to plug into the hw clock
>when I boot to BIOS setup. Then when I boot Linux, everything is
>correct.
>
>From the hwclock man page:
--utc Indicates that the Hardware Clock is kept in Coor-
dinated Universal Time. It is your choice whether
to keep your clock in UTC or local time, but noth-
ing in the clock tells which you've chosen. So
this option is how you give that information to
hwclock.
If you don't specify --utc when you should, or vice versa,
both setting and querying of the Hardware Clock will be
messed up.
If you don't use --utc, hwclock sets the hardware clock to locak time.
Mikkel
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
