Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Thursday 2007-12-06 at 17:58 -0800, Randall R Schulz wrote:
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.
Then you have the luck of getting a pretty good crystal. That's just a
matter of luck. One second per day is 0.0000116 or 0.00116% error.
Normal wrist watches are usually specified to 4 seconds per day at
worst. Two seconds is typical.
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!
Clearly this represents a gross hardware failure or a similarly extreme
software problem.
As the problem started the very same day I upgraded to suse 10.3, that
points to software.
I note that you keep stating that you UPGRADED from 10.2 to 10.3. Does
this mean a NEW installation? If not, is it possible that there is old
10.2 crud hanging around causing you lack of sleep?
Ciao.
--
Past experience, if not forgotten, is a guide for the future.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
