Date: Fri, 30 May 2008 20:12:41 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Robert Blayzor <rblayzor.bulk@inoc.net> Cc: freebsd-stable@freebsd.org Subject: Re: Sockets stuck in FIN_WAIT_1 Message-ID: <20080530101241.GS1028@server.vk2pj.dyndns.org> In-Reply-To: <A1459A8E-3615-4C26-A622-AE068B638373@inoc.net> References: <483EAED1.2050404@FreeBSD.org> <200805291912.m4TJCG56025525@apollo.backplane.com> <14DA211A-A9C5-483A-8CB9-886E5B19A840@inoc.net> <200805291930.m4TJUeGX025815@apollo.backplane.com> <0C827F66-09CE-476D-86E9-146AB255926B@inoc.net> <200805292132.m4TLWhCv026720@apollo.backplane.com> <CCBAEE3E-35A5-4BF8-A0B7-321272533B62@inoc.net> <20080530081143.GI1028@server.vk2pj.dyndns.org> <20080530084724.GA37672@walton.maths.tcd.ie> <A1459A8E-3615-4C26-A622-AE068B638373@inoc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--h56sxpGKRmy85csR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-May-30 05:35:56 -0400, Robert Blayzor <rblayzor.bulk@inoc.net> wrot= e: >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= =20 >with a Cisco PIX or ASA. I believe they have "half closed" timers just fo= r=20 >this purpose... Perhaps a kernel tunable knob would be a nice=20 >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. --=20 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. --h56sxpGKRmy85csR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkg/0xkACgkQ/opHv/APuIc57wCfYBPPNnvo9y0C5/lj2tWGhLHT YZkAoMD4/fMKTSpK5GpkHS5Ti55yxWop =ae4V -----END PGP SIGNATURE----- --h56sxpGKRmy85csR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080530101241.GS1028>