Friday, July 03, 2020

Re: xtraceroute 0.9.2 / host(1) cmd / OpenBSD 6.7

On 2020/07/03 21:18, Kapfhammer, Stefan wrote:
> Hi,
>
> I get a strange error message when starting xtraceroute 0.9.2
>
> ---
>
> diode@sk | 0 | /usr/local/share/xtraceroute | $ xtraceroute skapf@skapf.de
> calltrace
> DEBUG: spinner_ref: "traceroute" count: 0 -> 1
> /usr/sbin/traceroute is there and looks OK.
> /usr/bin/host is there and looks OK.
> /usr/local/share/xtraceroute/xtraceroute-resolve-location.sh is there and looks OK.
> Loading texture from file "/usr/local/share/xtraceroute/earth.png"... Done!
> Texture size is 800x400
> Loading texture from file "/usr/local/share/xtraceroute/night.png"... Done!
> Texture size is 800x400
> Found a hosts.cache with 9548 entries.
> Can't open the database file /usr/local/share/xtraceroute/site_hosts.cache!(In mode r)
> Can't open the database file /home/sk/.xt/user_hosts.cache!(In mode r)
> Found a networks.cache with 260 entries.
> Can't open the database file /usr/local/share/xtraceroute/site_networks.cache!(In mode r)
> Can't open the database file /home/sk/.xt/user_networks.cache!(In mode r)
> Can't open the database file /home/sk/.xt/user_generic.cache!(In mode r)
> Known countries: 245
> Built-in database: 95
> DEBUG: spinner_ref: "host" count: 1 -> 2
> Strange version of the "host" program found!
> I can't use this, see the man page for details.
> DEBUG: spinner_unref: "host" count: 2 -> 1
>
> ---
>
> In /usr/local/share/xtraceroute/xtraceroute-resolve-location.sh in line 72 I found
>
> RESPONSE=`$HOST -t LOC -x $STRING 2>&1`
>
> where $HOST is the path to the host(1) program
> When I look in the man page for host(1) there are options
>
> host [-46aCdilrsTVvw] [-c class] [-m flag] [-N ndots] [-R number]
> [-t type] [-W wait] name [server]
>
> But no -x option.
>
> Is there a workaround or bugfix?
>
> Regards,
> Stefan

This is because it used the "usage" output when you run host with no
command line options to detect the type of host program (BIND-like or
another old one). I've just committed a patch to -current ports so
that it can cope.

No comments:

Post a Comment