-----Original Message-----
From: Dave Hart [mailto:[email protected]]
Sent: Saturday, July 07, 2012 7:34 PM
To: Justin Piszcz
Cc: [email protected]
Subject: Re: [Pool] X9SCM-F-O clock drift +1 second into the future when ntp
running?
Something's unhappy. I'd add "noselect" to the server 127.127.28.0
line so it uses only the network sources to steer the clock and see if
eventually the offset and jitter for network sources comes down into
the range you see on the other supermicro system. If it does and the
jitter for the SHM driver settles down to better than the jitter from
network sources, you can use the offset of the SHM driver to tweak
your fudge and remove noselect to once again enable ntpd to steer the
clock to match the SHM driver. Keep an eye out for repeated steps --
that's a sign your clock rate is off by more than 500 PPM.
Good luck,
Dave Hart
--
Thanks, overnight, it did come down:
$ ntpq -pn
remote refid st t when poll reach delay offset
jitter
============================================================================
==
*127.127.28.0 .SHM. 0 l 7 16 377 0.000 13.537
5.075
+64.6.144.6 128.252.19.1 2 u 30 64 377 68.393 -3.682
1.400
-204.235.61.9 209.51.161.238 2 u 41 64 377 46.560 -15.125
1.302
-108.61.73.244 129.7.1.66 2 u 9 64 377 23.200 -10.460
2.064
+67.18.187.111 38.106.177.10 2 u 6 64 377 50.089 -7.486
2.403
However I'll still talk to SM because my other board looks like this after 5
min from boot, not sure why this one takes so long to come down to normal
levels.
Justin.
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
