| From: |
"Steven Levine" <ecs-isp@2rosenthals.com> |
Full Headers
Undecoded message |
| Subject: |
Re: [eCS-ISP] socket - no buffer space availble |
| Date: |
Wed, 30 Jul 2025 11:15:47 -0700 |
| To: |
"eCS ISP Mailing List" <ecs-isp@2rosenthals.com> |
|
|---|
In <list-13730074@2rosenthals.com>, on 07/30/25
at 10:02 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi Massimo,
>>>> 0 STREAM 42164 http..80 217.182.195.225 FIN_WAIT_2
>>>> 0 STREAM 56842 https..443 103.42.4.140 FIN_WAIT_2
>>>> 0 STREAM 18331 http..80 51.68.111.239 FIN_WAIT_2
>>>> 0 STREAM 62505 http..80 91.225.160.193 FIN_WAIT_2
>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.
Steven
--
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net> Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------
|