On 10 Apr 99, at 19:45, Bud Rogers wrote:
>
> "Michael Doerner" <[EMAIL PROTECTED]> writes:
>
> > BUT, after the next rebooting the time is gone back an hour again and I
> > will have to start the whole story again which I can't believe to be the
> > proper way.
>
> Sounds like your CMOS clock has gotten set back an hour. You are
> resetting the system clock in linux, but the CMOS clock is still an hour
> off. The clock command checks and sets the CMOS clock. Man clock for
> details.
>
> #clock -r to read the CMOS clock. I'll bet it's an hour off.
>
> Get your system clock set right, as you have been doing, then as root,
>
> #clock -w to write correct system time to the CMOS clock.
>
> You might want to do clock -r again just to be sure it worked. Then next
> time you reboot, your time should be right.
>
>
I have experienced the exact same problem. The questions is,
isn't Yast or SuseConfig doing something wrong here? If the
solution is to do a "clock -w", shouldn't Yast/suseconfig be
doing this as part of the standard procedure? Yast is, after
all, referring to the hardware clock itself in it's dialog and
implying that it will take care of it. Perhaps this was fixed
in 6.0 (which I still haven't gotten to yet...)?
-Bob
--
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
