[ntp:questions] nptq -p slowness
Richard B. Gilbert
rgilbert88 at comcast.net
Sun Jan 28 22:19:57 UTC 2007
Serge Bets wrote:
> Hello Chris,
> On Saturday, January 27, 2007 at 22:57:31 -0600, tomnykds at comcast.net wrote:
>>Did you try ntpq -p -n?
> Also slow, because of exact same DNS A requests on "DCF" and "LOCL"
> refid names. Apparently -n disables only the reverse resolution of the
> "remote" column:
> | $ ntpq -pn
> | remote refid st t when poll reach delay offset jitter
> | ==============================================================================
> | *127.127.28.0 .DCF. 0 l 60 64 377 0.000 0.180 0.144
> | 127.127.1.0 .LOCL. 8 l 16 64 377 0.000 0.000 0.004
The bug is that ntpq should not be interpreting the refid at all! It's
a text string, not an IP address and should not be treated as one. Yes,
sometimes the refid IS an IP address but it still should be treated as a
simple text string!
More information about the questions