[ntp:questions] Re: Question: Why does ntpd keeps a fixed difference from localhost ??

mike cook michael.cook at wanadoo.fr
Tue Nov 11 23:54:13 UTC 2003


The first odd thing is that your ntpdate -qd localhost is showing a very
long time to response
originate timestamp: c351ac7c.90e22000  Tue, Nov  4 2003 12:41:32.565
transmit timestamp:  c351ac83.6f2d9000  Tue, Nov  4 2003 12:41:39.434
  that's not far off 7 seconds.
NTP is very efficient, and should return a response in a few milliseconds.

Also , your local clock is missing polls
  LOCAL(0)        LOCAL(0)         3 l   67   64  377     0.00    0.000 
that looks odd, is your system so heavily loaded with higher priority 
tasks that ntpd isn't getting a look in?

Looking at your configuration you seem to be a sf12k domain , with one 
of your SC's as the selected time source.
You should look at the Sun Blueprint
"Using NTP on Sun Fire 15k 12 Servers"

It says that you shouldnt be using slewalways. I've not looked at 12k
configs for a while to see in what conditions that is valid.


Also check bugs 4510625 and 4656724 .


More information about the questions mailing list