[ntp:questions] nptq -p slowness

Danny Mayer mayer at ntp.isc.org
Mon Jan 29 04:17:19 UTC 2007

Harlan Stenn wrote:
>>>> In article <0eednfx366oTvCDYnZ2dnUVZ_u-unZ2d at comcast.com>, "Richard B. Gilbert" <rgilbert88 at comcast.net> writes:
> Richard> The bug is that ntpq should not be interpreting the refid at all!
> Richard> It's a text string, not an IP address and should not be treated as
> Richard> one.  Yes, sometimes the refid IS an IP address but it still should
> Richard> be treated as a simple text string!
> How can the code tell the difference between a refid that is a string and
> one that is an IP address?
> I want to stop doing this resolution altogether, but the last time I asked
> Dave about this he said he wanted to keep the lookup in place, even though
> it is only useful for IPv4.

Let me repeat myself. The refid should *never* be looked up. It's an ID
and not an address. Similarly refclocks themselves should not be looked
up and we should know that. This is a bug plain and simple and it should
 be logged as such.


More information about the questions mailing list