Michael Perry <[EMAIL PROTECTED]> wonders:
>So, let me get this straight. We have a value called timezone in
>rc.config but exactly what does setting this value accomplish?
It sets up a symlink, in my case:
/etc/localtime -> /usr/lib/zoneinfo/US/Pacific
and probably some other things like that, that let your machine
know what time zone you're in.
> Here is what I think should happen. I think that timezone should
>patrol the clock and when time changes it effects a change to the
>system clock and makes the computer change.
When I first set up my machine, I set the date using the most accurate
time I had handy (the cable TV schedule). That set the system clock,
the software clock. Then I manually syncronized the computer's
hardware clock using the command:
hwclock --systohc
which writes the system clock to the hardware one. I like "hwclock"
over "clock" because its name is more explicit. I think they do
the same things, with different syntax.
Then I added a line in /root/bin/cron.daily.local
that says:
/sbin/hwclock --systohc
and every night the system time is written to the hardware clock.
There are adjustment strategies discussed in the Howto, I believe,
that can keep the system clock very accurate. The hardware clock
will never be very accurate, but should keep you reasonable between
reboots.
>Rebooting to set the clock on the bios seems rather strange.
Oh, please... :) With luck you should reboot when you change
installations, or need to crack the case or something.
Cheers,
Jim
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
