Mailinglist Archive: opensuse-kde (310 mails)
| < Previous | Next > |
Re: [SLE] Speaking of time?
- From: Christopher Mahmood <ckm@xxxxxxxx>
- Date: Thu, 9 May 2002 17:11:59 -0700
- Message-id: <20020510000920.GB4772@xxxxxxxxxxxxxxxxxx>
Patrick,
Did you notice that the trailer on each message on suse-kde says not
to crosspost?
* Patrick (tracerb@xxxxxxxxxxxxxx) [020509 17:03]:
> Anthony brought up the subject of time/date being wrong on his mails,
> but my problem is somewhat different. This seems to be a problem that
> goes back to the 7.1 days! Each time I boot up, the system clock has
> the wrong time and requires resetting. The bios clock is correct as I
> have checked that already.
This sounds vaguely familiar...
> Going back to a previous mail when the problem showed up back in October
> 2001, it seems to be a bug in the /etc/rc.d/boot script which will
> cause the system clock to NOT be set to the hardware clock on boot.
> The bug has been around for quite some time it seems. The problem was
> simple in that adding the full path to the hwclock command solved the
> problem. The solution was to change the CLOCKCMD=hwclock in
> /etc/rc.d/boot file to CLOCKCMD=/sbin/hwclock and for good measure also
> adding /sbin/hwclock --hctosys in the /etc/rc.d/boot.local file!
Ah ha! I don't know where you guys are digging this stuff up at but
here's my response the last time someone posted this:
http://lists.suse.com/archive/suse-linux-e/2002-Mar/0390.html
--
-ckm
Did you notice that the trailer on each message on suse-kde says not
to crosspost?
* Patrick (tracerb@xxxxxxxxxxxxxx) [020509 17:03]:
> Anthony brought up the subject of time/date being wrong on his mails,
> but my problem is somewhat different. This seems to be a problem that
> goes back to the 7.1 days! Each time I boot up, the system clock has
> the wrong time and requires resetting. The bios clock is correct as I
> have checked that already.
This sounds vaguely familiar...
> Going back to a previous mail when the problem showed up back in October
> 2001, it seems to be a bug in the /etc/rc.d/boot script which will
> cause the system clock to NOT be set to the hardware clock on boot.
> The bug has been around for quite some time it seems. The problem was
> simple in that adding the full path to the hwclock command solved the
> problem. The solution was to change the CLOCKCMD=hwclock in
> /etc/rc.d/boot file to CLOCKCMD=/sbin/hwclock and for good measure also
> adding /sbin/hwclock --hctosys in the /etc/rc.d/boot.local file!
Ah ha! I don't know where you guys are digging this stuff up at but
here's my response the last time someone posted this:
http://lists.suse.com/archive/suse-linux-e/2002-Mar/0390.html
--
-ckm
| < Previous | Next > |