> Test will be ok if traceroute is in PATH. But if i make test with common user,
> traceroute is in /usr/sbin and this path is not included for common user.
> May be you can test if witout is ok, else check /usr/bin and /usr/sbin, then
> warn user if you can't find it ...
Path is precisely for managing these sorts of decisions. A "bug"
or "note" section in the documentation noting this "feature" is
certainly warranted, but I believe that searching for the executable
should be out of the scope of a package that parses the system
traceroute.
A test case that checks for the presence of traceroute in path
would probably be a good idea as well.
