Ok...one of the programers read my last email, and didn't feel I explained the
problem properly, so here is the same problem worded differently:
The problem is sometimes the client side does not close the socket even when the
server application is dead.
ps will show that the server is gone. However, [ netstat -an | grep 41797 ]
reveals that the client still holds on to the connection with a FIN_WAIT_2
state.
tcp 0 0 10.0.21.27.41797 10.0.21.127.1179
FIN_WAIT_2
My guess, this should clear itself after about 10 minutes.
When the client releases the connection, the state will be TIME_WAIT for about 2
to 20 seconds
tcp 0 0 10.0.21.27.41797 10.0.21.127.1179
TIME_WAIT
Question: I don't want to wait; how do I force these lingering connection
shadows to disappear.
Note: netstat -z claims to kill everything, which is not acceptable.
Jonathan Williams
Unix Systems Administrator
The Shubert Organization, Inc.
----- Original Message -----
From: "Jonathan Williams" <jonathw_at_shubertorg.com>
To: <tru64-unix-managers_at_ornl.gov>
Sent: Wednesday, October 16, 2002 4:46 PM
Subject: Clearing a port
> It's a simple enough question. We are running Tru64 5.1 and 5.1a on ES40 and
> ES45 machines. Is there a command to clear out a port? Basically, what
> happened today was that one of our production pieces of software goes through
a
> certain port. This application got kind of hung up, and we couldn't get it
> started again. The reason turned out to be that the last person who accessed
> this program was still connected to the port. We had to actually go to that
> person's machine and turn it off to disconnect them from the port so that our
> application would come back up.
>
> Is there a command that would have disconnected this computer from this port
> without having to track down the computer? I'm sure there is...seems like
> something people might need to do now and again. TIA
>
> Jonathan Williams
> Unix Systems Administrator
> The Shubert Organization, Inc.
>
Received on Wed Oct 16 2002 - 22:12:55 NZDT