-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-12-06 at 17:26 -0800, Randall R Schulz wrote:
On Thursday 06 December 2007 17:16, Carlos E. R. wrote:
...
Please, remember that the system time does not use the cmos clock and battery at all. That's a different clock altogether. Plus, the cmos clock is running fine, I'm checking it at the moment.
"... at all ...?" I don't think this is really true, is it?
When the system starts up, the Linux kernel initializes it's notion of the current time from the mainboard's CMOS clock (which, on all machines built in the past twenty years or more, is powered and running even when the computer is powered down and even disconnected from the mains; that's in part what the battery is for).
I know that. I actually wrote a howto on that ;-) What I mean is that during normal system use it is not used at all. It is read on boot, and written on halt (and I think on NTP stop, by the script, not the daemon).
Thereafter, the Linux kernel updates its time based on a timer interrupt, also generated by local hardware, of course. These timers are, as has been noted, not particularly accurate and often exhibit considerable drift over even moderate real-time intervals.
Not really. I have been using this same machine without permanent network, and thus, no NTP, for years, and the clock drift was about a second or two per day.
Likewise, if the system cannot contact an NTP server, it has a reasonable guess as to the current time, and it makes do with that.
It should be able to keep accurate time for hours, even days. This was so with previous suse versions, but not with 10.3. It drifts minutes in half an hour. This is unthinkable! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHWKQStTMYHG2NR9URArE/AJ9SHN6YTdaAi7+u8O2CohAzKdNZVQCgl3/G x2t2RjuZSl4uB3bIbSQwCsU= =4bdy -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org