If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server... -- ~adj~ Ces mystères nous dépassent Feignons d'en être l'organisateur...
System clocks are notoriously poor and you can correct for them in Linux. There's a clock HOWTO somewhere that tells you how to do this. JDL Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
-- ~adj~ Ces mystères nous dépassent Feignons d'en être l'organisateur...
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
OK the URL for clock help is http://www.wdm.com/LDP/HOWTO/mini/Clock.html
or any other LDP mirror around the world.
/Dee
John D Lamb
System clocks are notoriously poor and you can correct for them in Linux. There's a clock HOWTO somewhere that tells you how to do this.
JDL
Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
-- ~adj~ Ces mystères nous dépassent Feignons d'en être l'organisateur...
I use a program called "ntpdate". Just run it with the time server of your choice found at www.time.gov with the following options and time server of your choice. ntpdate -b -v time-nw.nist.gov the "time-nw.nist.gov" is the url of a time server. It will synchronize your system clock with the gov time servers to 0.000000 sec accuracy. Bill W John D Lamb wrote:
System clocks are notoriously poor and you can correct for them in Linux. There's a clock HOWTO somewhere that tells you how to do this.
JDL
Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
-- ~adj~ Ces mystères nous dépassent Feignons d'en être l'organisateur...
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Re: [SLE] System clock too fast From: Robert Stia
To: "David A. Riggs" "David A. Riggs" wrote:
On Wednesday 10 October 2001 10:04 am, Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
I'm running a dual Celeron Abit BP6 and my clock loses around 8 minutes in a week. Running SuSE 7.1 with the stock 2.4.0-SMP-64GB kernel. I'm going the NNTP route currently, but I'd much rather solve the problem by correcting whatever is the root of it rather than simply covering up the symptoms.
David A. Riggs
You all should be happy with such a minor clock problem. How about every time you booted Suse 7.1 your bios clock was changed by 4 hours, or 2 hours and 28 minutes, or 3 hours and 19 minutes, or some other weird time.
I have posted here several times, and have seen others with the very same problem. No help at all. Very frustrating and mystifying. Beginning to really aggravate me. Suse doesn't even acknowledge such a problem exists. It does though, believe me. Redhat never did that.
Bob S.
Sorry, unless your machine is SMP, this is totally unrelated to the problem discussed in this thread. Have you tried replacing your BIOS battery? David A. Riggs
"David A. Riggs" a écrit :
Re: [SLE] System clock too fast From: Robert Stia
To: "David A. Riggs" "David A. Riggs" wrote:
On Wednesday 10 October 2001 10:04 am, Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
--------------<SNIP>--------------------------
Sorry, unless your machine is SMP, this is totally unrelated to the problem discussed in this thread. Have you tried replacing your BIOS battery?
David A. Riggs
As mentionned in the original message maybe not clearly enough, the machine indeed is SMP : 2xPII 266Mhz -- ~adj~ Ces mystères nous dépassent Feignons d'en être l'organisateur...
Alain DIDIERJEAN a écrit :
"David A. Riggs" a écrit :
Re: [SLE] System clock too fast From: Robert Stia
To: "David A. Riggs" "David A. Riggs" wrote:
On Wednesday 10 October 2001 10:04 am, Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
--------------<SNIP>--------------------------
Sorry, unless your machine is SMP, this is totally unrelated to the problem discussed in this thread. Have you tried replacing your BIOS battery?
David A. Riggs
As mentionned in the original message maybe not clearly enough, the machine indeed is SMP : 2xPII 266Mhz
I finally found a working solution by reading hwclock's man : I added the following script to /etc/cron.daily, named bbb_local_time : #!/bin/sh # # paranoia settings # umask 022 PATH=/sbin:/bin:/usr/sbin:/usr/bin export PATH hwclock --adjust # correct HW clock hwclock --hctosys # set SYS time from HW This seems to keep the time correct +/-2 seconds during working time (8-23). I might add a correction from a time server by midnight should the drift be more important. Still testing as it has been operating only three days.. -- ~adj~ Ces mystères nous dépassent Feignons d'en être l'organisateur...
On Friday 12 October 2001 03:34 am, Alain DIDIERJEAN wrote:
"David A. Riggs" a icrit :
Re: [SLE] System clock too fast From: Robert Stia
To: "David A. Riggs" "David A. Riggs" wrote:
On Wednesday 10 October 2001 10:04 am, Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
--------------<SNIP>--------------------------
Sorry, unless your machine is SMP, this is totally unrelated to the problem discussed in this thread. Have you tried replacing your BIOS battery?
David A. Riggs
As mentionned in the original message maybe not clearly enough, the machine indeed is SMP : 2xPII 266Mhz
Errhm, I was replying to a Mr. Robert Stia who was complaining of something that seems more on-topic after reading the 'hwclock' man... Also after reading the 'hwclock' man, I'm going to try a similar approach to using 'hwclock --adjust' and 'hwclock --hctosys' along with a periodic NTP update....It's been so long since I've booted my duallie up into Win2k, that I can't remember whether to blame the Hardware or System clock for my time instabilities (BP6 has quite a long list of quirks), so I think I'll feel better getting an unbiased outside time from the NIST every day or so. David A. Riggs
On Wednesday 10 October 2001 10:04 am, Alain DIDIERJEAN wrote:
If I remember well, I read something about system clock being too fast on SMP computers. It's happening on my system since I installed kernel 2.4.10 SuSE (about 2mn a day). Can it be cured ?, beside loading twice a day from a time server...
I'm running a dual Celeron Abit BP6 and my clock loses around 8 minutes in a week. Running SuSE 7.1 with the stock 2.4.0-SMP-64GB kernel. I'm going the NNTP route currently, but I'd much rather solve the problem by correcting whatever is the root of it rather than simply covering up the symptoms. David A. Riggs
On Wednesday 10 October 2001 09:59 pm, David A. Riggs wrote:
I'm going the NNTP route currently, but I'd much rather solve the
Errhm, that's Network Time Protocol NTP...although the Network News Transport Protocol has been some help as well :-) David A. Riggs
participants (5)
-
Alain DIDIERJEAN
-
Bill Wright
-
David A. Riggs
-
Dee McKinney
-
John D Lamb