> > You can easily convince me of this if you present a screenshot. :-) > > anth...@haruhi:~$ ntpq -p > remote refid st t when poll reach delay offset jitter > ============================================================================== > *mighty.poclabs. 192.43.244.18 2 u 458 1024 377 49.473 -4.411 0.692 > 216.14.97.75 .CDMA. 1 u 75d 1024 0 35.485 0.986 0.000 > -dev1-c.chg003.i 64.113.32.5 2 u 794 1024 377 28.729 2.318 5.065 > status.e3b.org 198.123.30.132 2 u 27d 1024 0 92.181 0.594 0.000 > -ns1.your-site.c 132.236.56.252 3 u 958 1024 377 17.203 0.155 3.868 > -point2.adamants 128.138.140.44 2 u 815 1024 377 82.715 -9.194 1.183 > -tantalum.srvcs. 192.43.244.18 2 u 449 1024 377 116.387 -20.240 16.535 > +ohgma.metrics.n 64.73.32.135 3 u 485 1024 377 0.201 -5.332 1.550 > tapehost.metric 63.240.161.99 3 u 799 1024 377 0.266 -2.758 0.328 > 172.16.1.31 .INIT. 16 u - 1024 0 0.000 0.000 0.000 > mysql.metrics.n .INIT. 16 u - 1024 0 0.000 0.000 0.000 > +Tao.metrics.net 172.16.1.1 4 u 815 1024 377 0.180 -3.593 0.698
Have you noticed, that 216.14.97.75 is unreachable? :-) Please have look on value "0" in "reach" column. Gabor _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
