On 6/15/09 2:38 PM, Rich wrote:
Is this sort of behaviour to be expected? Does this mean that the NTP
algorithm ought to be giving more weight to servers with shorter
delays? Or, perhaps, does it suggest that there might be something
wrong with the Stanford servers that is making them all
Hi, Dave --
Replying to:
As you can see, bigben is on the order of 10ms off from the consensus,
at least from ntp.davehart.net's perspective on a verizon business-class
DSL. I had also considered that the offset could be due to asymmetric
routing, but given the same ~10ms offset seen from
Richard B. Gilbert wrote:
The Delay values for some of the servers you have configured
are large enough to suggest that they are poor choices!
Agreed. Please note, though, that I didn't explicitly choose
these particular servers -- they came from pools.
This does suggest that even servers
Rich wrote:
[]
Recently, in order to spread out my time base somewhat, I tried adding
some outside servers (using the *.pool.ntp.org DNS names) to my NTP
configurations. Since doing this, I've noticed that the nearby
(Stanford) servers are uniformly off by several milliseconds, in
comparison
