Netstat provides a reasonable list of active sockets on the system and
the systems they are talking too. How do I go one step further and tie
that Socket to a local process?
I'm trying to find a way to track down processes hung talking to dead
clients. If I can match a PID with the info in netstat I can back
track and see if the system is still up.
Lee E. Parsons