Date: Wed, 28 May 2008 21:53:34 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Robert Blayzor <rblayzor.bulk@inoc.net> Cc: freebsd-stable@freebsd.org Subject: Re: Sockets stuck in FIN_WAIT_1 Message-ID: <483E36CE.3060400@FreeBSD.org> In-Reply-To: <B775700E-7494-42C1-A9B2-A600CE176ACB@inoc.net> References: <B42F9BDF-1E00-45FF-BD88-5A07B5B553DC@inoc.net> <1A19ABA2-61CD-4D92-A08D-5D9650D69768@mac.com> <23C02C8B-281A-4ABD-8144-3E25E36EDAB4@inoc.net> <483DE2E0.90003@FreeBSD.org> <B775700E-7494-42C1-A9B2-A600CE176ACB@inoc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Blayzor wrote:
> On May 28, 2008, at 6:55 PM, Doug Barton wrote:
>> That's a known problem with FreeBSD 4, which is now well past EOL. I
>> would suggest moving to FreeBSD 7 ASAP.
>
>
>
> Is it? I searched and searched and never found any hits or PR's
> regarding this.
Not sure where you looked then, but I not only saw the discussion
multiple times on various lists, I know I posted about our experiences
with it. :)
> When was it first fixed? 5.x? 6.x? or not until 7?
The reason I suggested moving to 7 is that it was branched most
recently, has the best new features, etc. If you have to jump FreeBSD
versions, this is the one that will get you the most bang for your
buck. If you aren't using SMP boxes and have a risk-averse
environment, the latest version of 6 will get you where you need to go.
Please also note that while this problem has been tweaked somewhat in
later versions, it's not always a problem that can be "fixed" in the
OS. I'm guessing that you're using an Apache web server, since this is
the application that most often leads to this problem. There used to
be some helpful hints on Apache's web site for ways you can tune it to
reduce the problem, not sure if they're still there or not.
hth,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?483E36CE.3060400>