Hello Managers,
I have a 4100 running 4.0f PK4, (I thought I'd do that right away before
I forget). Anyway here's my question:
When I run a netstat -a I get an output of many lines like the following on
port 52100:
......
tcp 0 0 d0pey-100mb-1.52100 d0pey-100mb-1.3369
CLOSE_WAIT
tcp 0 0 d0pey-100mb-1.3369 d0pey-100mb-1.52100
FIN_WAIT_2
tcp 0 0 d0pey-100mb-1.52100 d0pey-100mb-1.3377
CLOSE_WAIT
tcp 0 0 d0pey-100mb-1.52100 d0pey-100mb-1.3379
CLOSE_WAIT
tcp 0 0 d0pey-100mb-1.52100 d0pey-100mb-1.3381
CLOSE_WAIT
tcp 0 0 d0pey-100mb-1.3381 d0pey-100mb-1.52100
FIN_WAIT_2
tcp 0 0 d0pey-100mb-1.52100 d0pey-100mb-1.3383
CLOSE_WAIT
tcp 0 0 d0pey-100mb-1.3383 d0pey-100mb-1.52100
FIN_WAIT_2_WAIT
.....
How can I connect this output to a process? Which client process is cauing
this? The way we just used was to suspend likely suspect processes and see
if the messages stop. But as you can probably guess, this is time consuming.
Is there a faster way in Tru64?
Jim Fitzmaurice
jpfitz_at_fnal.gov
UNIX is very user friendly, It's just very particular about who it makes
friends with.
Received on Wed Nov 08 2000 - 20:36:23 NZDT