Bug in Tiger check_listening_procs?

[Michael West <web@mitzit.net>]

     If I have found a bug then I will file a bug report.
     My knowledge is imperfect.  I thought I would check here first
     before filing.

     I am getting a report from tiger that squid is listening UDP on a high
     port.  This is not the peer cache listener as I have disabled that
     with the "-u0" squid command line option.

     `lsof -nPi | grep squid` gives:

     squid     19509     root    5u  IPv4 2036491       UDP *:32814 
     squid     19509     root   12u  IPv4 2036495       TCP 127.0.0.1:3128 (LISTEN)
     
     My understanding is that this UDP port is used by squid for its DNS
     client.  I do not understand why squid would want to bind to a port
     for this. The port number changes when I restart squid.

     Tiger reports this as listening on port 32814, which I do not think
     is correct.  

     If lose is found on the system 
     /usr/lib/tiger/systems/Linux/2/check_listeningprocs uses the
     command:

     $LSOF -nPi | $GREP "IPv" | $GREP -v "\->" | $AWK '{printf("%s %s %s
     %s\n", $1, $3, $7, $8)}' | $SORT | $UNIQ |
     
     It seems that it should `grep LISTEN` as well.  

     Comments?