The Saturday 2003-11-22 at 22:19 -0500, Krikket wrote:
This is documented in the sdb and elsewhere.
Eh? Mind posting more info, or a link to it? I'm not sure what sdb is,
You should... SDB: SuSE Support knowledgebase It is on the SuSE web page, and also locally, at least up to SuSE 8.2. Search for CMOS or clock: * Rating (CPU) (19.06.2002) * iSeries: Time on the Linux partition is not correct (23.04.2002) * After booting the system clock is set wrong * Setting the clock to GMT (Greenwich Mean Time) -> * Your Computer Clock Shows the Wrong Time
or what you're getting at with the "two clocks" and all.
Every Personal Computer modeled after the IBM XT or AT since the eighthes
has got two clocks :-)
See "man hwclock", section "Clocks in a Linux System" for a good
explanation of this.
The subject has been talked about on this list several times. Just do a
search for "keep time":
|> Date: Fri, 18 Apr 2003 18:54:27 +0100
|> From: Keith Powell
I've been having a problem with the clock in KDE running slow -- as much as 10 minutes in a 30 minute period.
Compare the clock shown by KDE with the output from the command "date" on a console: they might be different, and if they are, it is kde who is wrong. Do this before doing any other change.
I don't understand why deleting the scripts to keep the clocks in synch would be a "good thing"...
Not certainly the script, but a data file used by the boot script (actually, bu hwclock) to know the amount the clock is going fast or slow. The boot script will recreate it. A paste from another of my posts: CR> No, I don't think is the hardware, nor the software: It is the user CR> ;-) CR> CR> It is explained somewhere on the suse SDB. What I understand is - more CR> or less -, that if you change, say, your system clock one hour fast CR> (but only system time, not hardware time) when the computer is halted, CR> the halt script notes the difference of one hour, and will save on the CR> adjustment file that the clock is slow by, say, one hour every day: so CR> the boot script will make the adjustment automatically when you boot CR> up. CR> CR> That is the idea, but of course, thinking that you want to compensate CR> seconds or minutes at the most, and that you had set it to the exact CR> time and seconds the first time. CR> CR> If you - we :-) - are not doing that, it is better that we delete the CR> adjustment file to disable the automatics, at least for this once. CR> CR> Then, if you use xntp or similar, or even the radio, the adjustment CR> will be made with exactitude, and the scripts will work as expected. Finally, if nothing of this helps, there are some chipsets that have known problems keeping time with Linux. Also, suspending the computer may throw the clock way off. -- Cheers, Carlos Robinson