:If it is a Linux only machine, set the clock to utc and forget about the
:time change - Linux will handle it for local times for most time zones.
:(Don't forget to change /etc/sysconfig/clock...)
Yes, and one other thing that I discovered on my laptop -- if you have
an APM-capable machine and you use the suspend or "sleep" feature,
check your APM script (/etc/sysconfig/apmd), and make sure it's using
the -u option. By default (mine are custom), I think it's supposed to
check to see if your hardware clock uses GMT and set that option for
you automatically. I don't trust that, and so set it definitively.
If this is wrong, your clock will jump an amount equivalent to your
GMT differential every time you resume. =)
-d
:
:As for your clock being off, PC clocks are not known for accuracy. Also,
:if you have set the hardware clock from Linux, there is now an adjustment
:factor that is applied when ever you reboot. (/etc/adjtime) It can have
:some interesting affects if you use hwclock to change for daylight savings
:time... On the other hand, it you set the hardware and software clocks
:weekly for an accurate source, it can do a very good job of keeping your
:clock on 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.
