Re: Sockets stuck in FIN_WAIT_1

On 2008-May-30 05:35:56 -0400, Robert Blayzor <rblayzor.bulk@xxxxxxxx> 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
session...

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
option/fix/hack also.

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.

--
Peter Jeremy
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.

Attachment: pgpU1EYSB5hWQ.pgp
Description: PGP signature