From owner-freebsd-stable@FreeBSD.ORG Thu May 29 05:59:54 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 98D4D106564A for ; Thu, 29 May 2008 05:59:54 +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 42AD58FC14 for ; Thu, 29 May 2008 05:59:54 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 3379 invoked by uid 399); 29 May 2008 06:11:41 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 May 2008 06:11:41 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <483E4657.9060906@FreeBSD.org> Date: Wed, 28 May 2008 22:59:51 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080525) MIME-Version: 1.0 To: Mark Kirkwood References: <1A19ABA2-61CD-4D92-A08D-5D9650D69768@mac.com> <23C02C8B-281A-4ABD-8144-3E25E36EDAB4@inoc.net> <483DE2E0.90003@FreeBSD.org> <483E36CE.3060400@FreeBSD.org> <483E3C26.3060103@paradise.net.nz> In-Reply-To: <483E3C26.3060103@paradise.net.nz> 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, Robert Blayzor 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 05:59:54 -0000 Mark Kirkwood wrote: > Doug Barton wrote: > The Apache page: > > http://httpd.apache.org/docs/2.3/misc/perf-tuning.html > > It mentions FIN_WAIT_2 not 1, so this might be a different/new problem. IIRC it actually is the same problem, but in any case you're missing the bit where 4.x is EOL. :) Hence my advice to upgrade to 7.0 and try again, since on the off chance this actually IS a new problem, it stands the best chance of getting fixed. Doug -- This .signature sanitized for your protection