[EMAIL PROTECTED] wrote:
Ok, now the reach is 377 but it still does'nt work :-(
remote refid st t when poll reach delay offset
jitter
==============================================================================
*salukes.opensou 80.127.4.179 2 u 15 64 377 59.996 -22.493
9.712
+dsl-33.152.240. 128.250.36.2 2 u 10 64 377 404.650 -10.787
9.624
I'd say that the above server is an extremely poor choice! A round trip
delay of 404 milliseconds means that the potential error in transmitting
time from wherever he is to you, will be 202 milliseconds. I try to
use servers with round trip delays of 20 milliseconds or less.
+frog.de.20six.n 200.9.74.4 3 u 11 64 377 43.175 -28.222
15.299
LOCAL(0) LOCAL(0) 5 l 11 64 377 0.000 0.000
0.001
I also noticed that none of your server statements in ntp.conf contains
the "iburst" keyword. Iburst causes the first eight request packets
sent to each server to be sent at two second intervals. This gets ntpd
enough information to start synchronizing your clock in twenty seconds
as opposed to a little over five minutes. After the initial burst of
eight packets, ntpd will send queries at the normal minimum poll
interval of 64 seconds.
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
