On Thu, 11 Sep 2003 09:32:30 +1000
David Cureton <david.cureton@catapult.com> wrote:
> This was background work so my debugging process was probably not very
> 'scientific'
True. To check to see what ntp is doing just use ntpq.
{grey@teleute:~} ntpq localhost
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
*clock.fmt.he.ne .GPS. 1 u 841 1024 377 22.544 -1.610 34.667
+63.247.194.250 time-B.timefreq 2 u 831 1024 377 74.265 -4.978 1.713
-dev.tummy.com tock.usnogps.na 2 u 833 1024 377 73.215 -37.790 11.506
+decimal.lib.ci. ntp0.usno.navy. 2 u 896 1024 377 36.849 -10.525 23.543
Peers lets you know what peers you have and how close/far off they are to
your current time. By looking at it you can quickly pick out the servers
which might not be helping all that much. In the above example dev.tummy.com
is clearly outta whack. In fact it appears ntpd has decided not to use it.
--
Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
PGP Key: 8B6E99C5 | main connection to the switchboard of souls.
-------------------------------+---------------------------------------------
Attachment:
pgp6aX7zhDFiD.pgp
Description: PGP signature