Various suggestions were offered, ranging from
'possible miss-set DNS server' to
'have you been hacked'
Joe Mario, a Compaq software engineer, sorted
me out. The problem was with kloadsrv. Its
message q was full due to outstanding requests
from jobs which have since died.
Restarting kloadsrv fixed the netstat problem.
Next task is to track down the cause of the
full q...
Many thanks to:
Joe Mario
Joe Fletcher
Jim Belonis
Judith Reed
Original message:
>Hi all,
>
>ES40, TU64 5.0A, patchkit1.
>
>netstat hangs indefinitely on this system.
>A trawl through the archives suggests that
>netstat -n (to prevent addr-to-name translation)
>might be a workround, but not for me unfortunately.
>
>ifconfig -a shows:
>
>fta0: flags=8c62<BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
>
>lo0: flags=100c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX,NOCHECKSUM>
> inet 127.0.0.1 netmask ff000000 ipmtu 4096
>
>sl0: flags=10<POINTOPOINT>
>
>tu0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
> inet 131.111.85.78 netmask ffff0000 broadcast 131.111.255.255 ipmtu
>1500
>
>tu1: flags=c62<BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
>
>tu2: flags=c62<BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
>
>tu3: flags=c62<BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
>
>This *IS* correct, only tu0 is in use.
Received on Wed Jan 24 2001 - 17:05:17 NZDT