On Mon, Sep 12, 2005 at 12:03:27PM -0700, maxim wexler wrote:
> > what about the output from "hwclock"? run it as
> > root, does it give the
> > same time/date as "date"?
> >
>
> the same. In fact when I update the time w/ date -s
> hwclock continues to give the incorrect one. Until a
> reboot when both will give the incorrect original time
> plus whatever time has elapsed since the first boot of
> the day.
>
hum... fishy!
On Mon, Sep 12, 2005 at 12:20:55PM -0700, maxim wexler wrote:
> > check out /etc/conf.d/clock
> >
> # /etc/conf.d/clock
>
> # Set CLOCK to "UTC" if your system clock is set to
> UTC (also known as
> # Greenwich Mean Time). If your clock is set to the
> local time, then
> # set CLOCK to "local".
>
> CLOCK="UTC"
^
|
Problem #1.
>
> # If you wish to pass any other arguments to hwclock
> during bootup,
> # you may do so here.
>
> CLOCK_OPTS=""
>
> # If you want to set the Hardware Clock to the current
> System Time
> # during shutdown, then say "yes" here.
>
> CLOCK_SYSTOHC="no"
>
^
--- |
|
THIS is your problem #2.
Date only manipulates the kernel clock. If you don't sync it with your
hardware clock, how do you expect the computer to remember the change?
During a power cycle, the kernel is not running, you know q=
Also, I'd wager that your clock is consistently off by the same number
of hours after each boot. Why? If the BIOS clock is correctly set to
the time in your time-zone, you need to set
CLOCK="local"
(see problem #1 above). Right now even though the BIOS clock is
correct, the software thinks that the time it is keeping is Greenwich
Mean Time, so it adds/subtracts the suitable number of hours according
to your timezone.
W
--
"This is obviously not how one does science, but in retrospect you get the right
answer." ~DeathMech, S. Sondhi. P-town PHY 205
Sortir en Pantoufles: up 32 days, 1:07
--
[email protected] mailing list
