From rob@ideal.net.au  Tue Dec 14 14:48:42 1999
Return-Path: <rob@ideal.net.au>
Received: from mail.ideal.net.au (fragile.ideal.net.au [203.20.241.5])
	by hub.freebsd.org (Postfix) with ESMTP id 6DEE914F6C
	for <freebsd-gnats-submit@freebsd.org>; Tue, 14 Dec 1999 14:48:38 -0800 (PST)
	(envelope-from rob@ideal.net.au)
Received: from localhost (rob@localhost)
	by mail.ideal.net.au (8.9.3/8.9.3) with SMTP id JAA26668;
	Wed, 15 Dec 1999 09:46:39 +1100 (EST)
Message-Id: <Pine.BSI.3.96.991215094000.24830E-100000@fragile.ideal.net.au>
Date: Wed, 15 Dec 1999 09:46:38 +1100 (EST)
From: Rob Wise <rob@ideal.net.au>
To: Gene & <stark@cs.sunysb.edu>
Cc: freebsd-gnats-submit@freebsd.org
In-Reply-To: <199912142233.RAA28583@bsd7.cs.sunysb.edu>
Subject: Re: TCP connections in CLOSING state (kern/14026)

>Number:         15487
>Category:       kern
>Synopsis:       Re: TCP connections in CLOSING state (kern/14026)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 14 14:50:00 PST 1999
>Closed-Date:    Fri Dec 17 12:41:33 PST 1999
>Last-Modified:  Wed Oct 26 06:02:23 GMT 2005
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 On Tue, 14 Dec 1999, Gene & wrote:
 
 > I was just reading your bug report (kern/14026) in the GNATS database,
 > and Garrett Wollman's response.
 > 
 > A few hours ago, I updated a busy web server from FreeBSD 2.2.5 to
 > FreeBSD 3.2.  I have more or less immediately noticed the accumulation
 > of TCP connections in the CLOSING state.  This causes me difficulty
 > with respect to stopping and starting the custom web server I am
 > running on this host.
 > 
 > FreeBSD 2.2.5 did not suffer from this problem, so either I have to
 > disagree with Garrett in his assessment that "this is how TCP works",
 > or there have been some other TCP parameters that have been introduced
 > with new or different values between 2.2.5 and 3.2.
 > 
 > Did you figure out any solution to your problem?  I'd be interested
 > to hear if you did.  Thanks.
 
 Hi Gene,
 
 I have recieved no further contact from the FreeBSD team about the
 problem, but I believe someone may have fixed it shortly after I submitted
 this PR.  I have a machine running a later 3.3-STABLE, and one with 3.4-RC
 and neither show this problem any more.
 
 I think 3.4 will be out some time in the next month, and shouldn't have
 this problem any more.
 
 The machine I have that doesn't show this problem is running a kernel:
 
 FreeBSD no2.ideal.net.au 3.3-STABLE FreeBSD 3.3-STABLE #2: Tue Nov 30
 11:18:15 EST 1999
 
 Cheers,
 
 Rob
 
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Fri Dec 17 12:41:33 PST 1999 
State-Changed-Why:  
Intended as a followup to kern/14026. 
>Unformatted:
