Rodolfo J. Paiz wrote:
On Sat, 2004-11-06 at 12:34 -0500, Bob Goodwin wrote:It's interesting [to me anyway] to note that the only thing that changed in readings taken at sleep 5 seconds and 1000 seconds is the "jitter."
However, even with the 5 seconds I believe it's correcting the clock? Or does running ntpq upset things somehow? Result in less than optimum correction?
ntpq will not disturb anything and you may safely query it as many times as you like. However, it will probably show your clock as being somewhat off... it is the clock *adjustment* which is going to take several minutes to begin approaching something useful.
Cheers,
~ ./tsync
Shutting down ntpd: [ OK ]
ntpd: Synchronizing with time server: [ OK ]
Starting ntpd: [ OK ]
remote refid st t when poll reach delay offset jitter
==============================================================================
ntp-1.cns.vt.ed 198.82.247.40 2 u 4 64 1 142.980 -1.958 0.004
ntp-4.cns.vt.ed 198.82.247.40 2 u 3 64 1 136.884 1.147 0.004
ntp2.jrc.us 65.211.109.12 2 u 2 64 1 149.864 -0.395 0.004
ntp1.jrc.us 129.7.1.66 2 u 1 64 1 145.863 -2.138 0.004
remote refid st t when poll reach delay offset jitter
==============================================================================
*ntp-1.cns.vt.ed 198.82.247.40 2 u 494 512 37 142.980 -1.958 4.842
+ntp-4.cns.vt.ed 198.82.247.164 2 u 488 512 37 136.884 1.147 5.211
+ntp2.jrc.us 65.211.109.12 2 u 490 512 37 146.899 0.339 4.299
+ntp1.jrc.us 129.7.1.66 2 u 484 512 37 145.863 -2.138 4.267
This using a tsync script:
~ tsync
service ntpd restart
sleep 5
ntpq -p
sleep 1000
ntpq -p
Either the "offset" value displayed after 5 seconds is as good as it gets or I have something configured wrong?
Bob Goodwin
