Sockets stuck in FIN_WAIT_1
peterjeremy at optushome.com.au
Fri May 30 10:12:46 UTC 2008
On 2008-May-30 05:35:56 -0400, Robert Blayzor <rblayzor.bulk at inoc.net> wrote:
>A timeout value would be fine.
The problem is selecting a sensible timeout - 30-60s might be reasonable
for a webserver that serves static content but is a bit short for a shell
>On a side note, I could easily fix this problem by frontending the server
>with a Cisco PIX or ASA. I believe they have "half closed" timers just for
>this purpose... Perhaps a kernel tunable knob would be a nice
I don't think your problem is related to half-closed connections. You
would get exactly the same behaviour if the server didn't close its
end of the connection. OTOH, a long-lived half-closed connection is
perfectly valid - many years ago, I wrote a tool that logged data in
one direction only and so closed the other direction.
I agree that a kernel tunable would be nice but I'm not in a position
to write a suitable patch at present.
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080530/c03004f7/attachment.pgp
More information about the freebsd-stable