On Tue, Oct 6, 2009 at 10:48 PM, Jeff Woolsey <[email protected]> wrote:
> Your reaches are even smaller now!  We can't really draw conclusions
> from single data points.  I'm not sure what the jitter of one point
> means. You're using iburst, though, so maybe that accounts for it.

i rm'd iburst from my /etc/ntp.conf last eve, and the box has run
since then ...  atm, i've

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+zorro.sf-bay.or 216.218.254.202  2 u   23   64   77   24.220  -829.09 493.664
*AC-NTP0.net.cmu 128.237.148.140  2 u   33   64   77   80.883  -807.14 491.659
+AC-NTP1.net.cmu 128.237.148.140  2 u   48   64   37   85.234  -772.44 404.404
 AC-NTP2.net.cmu 128.237.148.132  2 u   53   64   17   82.856  -761.93 313.603
+clock.sjc.he.ne .CDMA.           1 u    2   64   77   15.860  -879.75 484.443


reach of 77, and jitters ~ 400.

i admit, given this flopping around of data, i've no clue what's
good/correct/etc.

how _does_ one evaluate if ntp's functioning ok or not?  some
combination of data & vehavior over time, i'm sure ...

thanks.
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers

Reply via email to