Re: [opensuse] Bad kernel clock [Was: opensuse 11.0 x64 time messed up with dual boot - SOLVED]

Carlos E. R. wrote:


The Monday 2008-09-15 at 01:03 -0500, David C. Rankin wrote:

...

POLL INTERVAL CONTROL
...
maximum. However, this assumes the intrinsic clock frequency error is
small
enough for the discipline loop correct it. The capture range of the
loop is 500

You have just explained a double bug I noticed a few days ago.



-- Cheers,
Carlos E. R.


Hmm...

I am unwittingly passing FUD by quoting a man page -- interesting indeed. I
guess to be complete, I am forcing an update against specified external servers
in the /etc/ntp.conf file. Specifically:

server 71.170.251.21
server ntppub.tamu.edu
server 129.119.80.126
server 207.55.146.19

A ntp restart forces a ntpdate update from tick.greyware.com or
ntppub.tamu.edu which is the A&M server that is about 90 miles away.

Stopping ntp and using ntpdate also disclosed some strange behavior.
Specifically, several of my normal reliable servers were acting if the ntp
protocol has changed:

09:28 alchemy~> sudo rcntp stop
Shutting down network time protocol daemon (NTPD) done
09:29 alchemy~> sudo ntpdate ntppub.tamu.edu
16 Sep 09:29:44 ntpdate[19528]: no server suitable for synchronization found
09:29 alchemy~> man ntpdate
09:30 alchemy~> sudo ntpdate 129.119.80.126
16 Sep 09:31:30 ntpdate[19585]: no server suitable for synchronization found
09:31 alchemy~> sudo ntpdate 207.55.146.19
16 Sep 09:34:06 ntpdate[19591]: no server suitable for synchronization found
09:34 alchemy~> ping ntppub.tamu.edu
PING ntp3.tamu.edu (128.194.254.9) 56(84) bytes of data.
64 bytes from ntp3.tamu.edu (128.194.254.9): icmp_seq=1 ttl=55 time=20.3 ms
< hmm.. brief break taken >
11:08 alchemy~> sudo ntpdate tick.greyware.com
16 Sep 11:09:14 ntpdate[20573]: adjust time server 71.170.251.21 offset
-0.064101 sec
11:10 alchemy~> sudo rcntp start
ntpd: time slew -0.025542s
Starting network time protocol daemon (NTPD) done

I can't explain why some of the servers are not responding to the ntpdate
request as usual, but it does add to the ntp quandry.

However, I still rely on ntp to keep accurate time. I guess I'm just lucky, I
can go with my box shut down for days and still never have more than a 1 sec
slew on ntp synchronization.

For what it's worth, add this to the ntp mix.

--
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx