[ntp:questions] time delta between clients

Rick Jones rick.jones2 at hp.com
Thu Dec 13 18:32:56 UTC 2007


Doug Hughes <doug at will.to> wrote:
> well, I guess the point is, if you think it's going to be symmetric
> anyway (in your almost guaranteed sense), why not just simplify
> tremendously, run ping, and divide by 2?

Then it wouldn't be a unidirectional transfer :)

Being the clueless ntpadmin I am, I am not sure I did things correctly
with the suggestion to setup a peer association, and drop the polling
intervals, I went ahead and tried to do that with my two systems
anyway.  I also took away the "far away" time servers.

On bl480c1:
ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 bl480c2.raj     10.208.0.1       3 u   13   16  377    0.093   -0.002   0.017
*linger.raj      15.4.81.61       2 u    2   16  377    0.125    0.155   0.145
 LOCAL(0)        .LOCL.          10 l   56   64  377    0.000    0.000   0.001

On bl480c2, when I initially botched the peer line, saying bl481c1 by
mistake:

ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*linger.raj      15.4.81.61       2 u   11   16  377    0.139    0.550   0.089
 LOCAL(0)        .LOCL.          10 l   27   64  377    0.000    0.000   0.001

I corrected that - it was interesting to see how far things migrated
in just the 30 seconds or so ntpd wasn't running on bl480c2.  Shortly
after restarting, the offset reported by bl480c1 was 0.100 rather than
0.002.

rick jones
-- 
portable adj, code that compiles under more than one compiler
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...




More information about the questions mailing list