On 4/5/06, Vivek Khera <[EMAIL PROTECTED]> wrote:
> ISC's ntp is well known and understood and considered very accurate.
> I see no other choice.
 
 
After Running OpenNTP for a while now, I feel less uncomfortable with it - after the first 12 hours or so, the clock swings (+/-12ms) evened out, and it's staying quite comfortably within +/- 2-3ms with very little jitter.  In the following output of 'ntpq -c peers', the system in question is 'balrog-priv'; note the odd reference clock - I think that's an artifact of the minimal implementation that doesn't allow that level of querying.  In fact, for the most part it seems to stay well within 1ms (it refers to no-such-system, dies-irae, and the local system I'm querying from).

remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
localhost       .INIT.          16 l    - 1024    0     0.000    0.000 4000.00
+balrog-priv     17.4.247.255     5 u  125 1024  377    0.182   -0.056   0.040
-no-such-system  192.168.225.101  3 u  129 1024  377     0.527    2.654   0.171
-dies-irae       192.168.225.102  4 u  129 1024  377    1.359   -1.548   0.216
-helmsdeep       192.168.225.101  3 u   69 1024  377     0.312   -1.994   0.200
-barad-dur       192.168.132.249  4 u  115 1024  377    0.243   -1.300   0.401
-orthanc         192.168.225.101  3 u  114 1024  377     4.282    0.208   0.017
*bo-peep         192.168.225.101  3 u   49 1024  377    0.887   -0.048   0.046
-sheep           192.168.192.60   3 u   75 1024  377     0.657   -0.695   0.073
-sparky          192.168.225.102  4 u  113 1024  377    0.992   -1.055   1.515
-trogdor         192.168.252.191  4 u   14 1024  377     0.960   -4.816   0.671
+pudge           192.168.225.101  3 u  128 1024  377    0.489   -0.214   0.132
 

Reply via email to