>all the FIN_WAIT_2 have 0 as socket number
>if i use the scritp with:
>soclose 0
Opps my bad. I was not thinking clearly. As you found, that's never
going to work even if try to use unsupported command line operands.
Netstat is not reporting the original socket number. I have no idea if
this is by design or a netstat defect.
I wonder if a brute force approach might work - close the sockets that are
not listed as open as in
run netstat -s to collect a list of open sockets
for socket = 1 to 32767
if socket not in list
soclose socket
end
The stack knows the FIN_WAIT_2 socket number or it would not be able to
prevent it from being reused. The question is is there anything that can
be done to speed up to full release the socket resources.
Nazaj na seznam