From owner-freebsd-stable@FreeBSD.ORG Thu May 29 04:53:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A9C81065687 for ; Thu, 29 May 2008 04:53:37 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.freebsd.org (Postfix) with ESMTP id E57288FC28 for ; Thu, 29 May 2008 04:53:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 10423 invoked by uid 399); 29 May 2008 05:05:23 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 May 2008 05:05:23 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <483E36CE.3060400@FreeBSD.org> Date: Wed, 28 May 2008 21:53:34 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080525) MIME-Version: 1.0 To: Robert Blayzor References: <1A19ABA2-61CD-4D92-A08D-5D9650D69768@mac.com> <23C02C8B-281A-4ABD-8144-3E25E36EDAB4@inoc.net> <483DE2E0.90003@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Sockets stuck in FIN_WAIT_1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2008 04:53:37 -0000 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