On 27-Aug-98 Rafael Cordones Marcos wrote:
> By the way, (for anybody listening) when I live my PC on for several
> days I have found that the hardware clock and th system time differ in
> HOURS. Is that OK? Should I use cron to update the hardware clock
> every now and then?
Several hours is not good. Something is not working as it should.
Seconds, yes; minutes out after a few days, OK.
Anyway, something needs to be reset: hardware clock or system clock or
both.
1. clock -u -r will tell you what the absolute (UT/GMT) CMOS clock
is at the time
2. clock -r will tell you what the same time is, in your Timezone
3. date will tell you what the system date & time are, in your
Timezone
Compare the above with the best info you can get about what the time
really is.
4. read "man date"
5. date -s datestring will set the SYSTEM clock to what you specify
in your Timezone
6. clock -u -w will set the CMOS clock to UT/GMT corresponding to your
system time, allowing for Timezone
7. clock -w will set the CMOS clock to the same as your local time
(system time, not allowing for Timezone; if your
Timezone has an offset, then when system time is
re-read from the CMOS it will be wrong relative to
local time)
Cheers,
Ted.
--------------------------------------------------------------------
E-Mail: (Ted Harding) <[EMAIL PROTECTED]>
Date: 28-Aug-98 Time: 20:15:20
--------------------------------------------------------------------
