Re: [ntp:questions] making sense of stats offset values [or trying to...]

David Woolley wrote: Bruce Lilly wrote: [] # ntpq -p remote refid st t when poll reach delay offset jitter *megatron.blilly 18.26.4.105 2 u 27 64 377 2.9270.296 0.122 # ntptrace megatron.blilly.net: stratum 2,

Re: [ntp:questions] making sense of stats offset values [or trying to...]

David Woolley wrote: David J Taylor wrote: David Woolley wrote: Bruce Lilly wrote: [] # ntpq -p remote refid st t when poll reach delay offset jitter *megatron.blilly 18.26.4.105 2 u 27 64 377 2.9270.296 0.122 #

Re: [ntp:questions] making sense of stats offset values [or trying to...]

David J Taylor wrote: David Woolley wrote: Bruce Lilly wrote: [] # ntpq -p remote refid st t when poll reach delay offset jitter *megatron.blilly 18.26.4.105 2 u 27 64 377 2.9270.296 0.122 # ntptrace

Re: [ntp:questions] making sense of stats offset values [or trying to...]

Bruce Lilly wrote: offset jitter = LOCAL(0).LOCL. 10 l 17 64 377 0.0000.000 0.004 +fastener.blilly 192.168.99.703 u 37 64 377 2.8440.722 0.093 Apologies for the order of

[ntp:questions] making sense of stats offset values [or trying to...]

Running ntp version=ntpd 4.2@1.1541-o Mon Jan 19 15:18:44 UTC 2009 (1) as reported by ntpq, on opensuse 11.1 Linux, if that matters. I'm trying to make sense of the time offset numbers reported in loopstats and peerstats files and by ntptrace. The documentation is unclear on a few points, and