On 2014-06-29 02:25, James Knott wrote:
On 06/28/2014 07:46 PM, John Andersen wrote:
not because it is more accurate
Ummm... As I mentioned earlier, that's from the National Research Council, which provides Canada's primary time standard. If they're wrong then they've got a serious problem. Also, as I mentioned, my Android phone, running clocksync from that same server, agreed with the 2 NIST sources. So, if 3 agree and one doesn't, where do you think the problem is?
I don't know. The server seems almost correct: Telcontar:~ # ntpq --peers remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) .LOCL. 10 l 38 64 1 0.000 0.000 0.000 AmonLanc.valino 81.47.170.118 3 u 37 64 1 0.308 0.030 0.000 time.nrc.ca 132.246.11.232 2 u 36 64 1 176.844 -3.968 0.000 vps01.roethof.n .INIT. 16 u - 64 0 0.000 0.000 0.000 ntp01.srv.cat .INIT. 16 u - 64 0 0.000 0.000 0.000 ns1.indaloweb.n .INIT. 16 u - 64 0 0.000 0.000 0.000 numeros.vectric 158.227.98.15 2 u 32 64 1 63.919 -4.032 0.000 time.sunrise.ne 212.161.179.138 2 u 31 64 1 88.198 -0.070 0.000 91.240.0.5 .INIT. 16 u - 64 0 0.000 0.000 0.000 wtf.roflcopter. .INIT. 16 u - 64 0 0.000 0.000 0.000 laois.walcz.net .INIT. 16 u - 64 0 0.000 0.000 0.000 dns3.masbytes.e 81.19.96.148 3 u 27 64 1 119.634 0.350 0.000 Telcontar:~ # It is about 4 seconds slow, if that is what "offset" means. Another test later on (with daemon restart): Telcontar:~ # ntpq --peers remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) .LOCL. 10 l 36 64 1 0.000 0.000 0.000 AmonLanc.valino 81.47.170.118 3 u 35 64 1 0.322 0.016 0.000 time.nrc.ca 132.246.11.232 2 u 34 64 1 177.717 -3.221 0.000 dns3.masbytes.e 81.19.96.148 3 u 33 64 1 121.369 1.262 0.000 ns1.indaloweb.n .INIT. 16 u - 64 0 0.000 0.000 0.000 din-190-249-227 150.214.94.5 2 u 31 64 1 106.373 30.692 0.000 guti.uc3m.es .INIT. 16 u - 64 0 0.000 0.000 0.000 ntp0.as34288.ne .INIT. 16 u - 64 0 0.000 0.000 0.000 wtf.roflcopter. .INIT. 16 u - 64 0 0.000 0.000 0.000 87.117.251.3 .INIT. 16 u - 64 0 0.000 0.000 0.000 masip.celingest 158.227.98.15 2 u 26 64 1 84.042 5.674 0.000 91.240.0.5 .INIT. 16 u - 64 0 0.000 0.000 0.000 ntp0.dillydally .INIT. 16 u - 64 0 0.000 0.000 0.000 kvm01-vps.cleve .INIT. 16 u - 64 0 0.000 0.000 0.000 Telcontar:~ # so it is closing up. :-? In any case, it does not matter: you must have several servers defined. The protocol discards the bad ones automatically. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)