From owner-freebsd-bugs Tue Oct 10 13:31: 0 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id B9A9A37B502 for ; Tue, 10 Oct 2000 13:30:57 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Oct 2000 21:30:56 +0100 (BST) Date: Tue, 10 Oct 2000 21:30:55 +0100 From: David Malone To: "Jim D." Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/21791: Hang on FIN_WAIT_2 Message-ID: <20001010213055.A27861@walton.maths.tcd.ie> References: <200010101930.MAA67954@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010101930.MAA67954@freefall.freebsd.org>; from jd@dynw.com on Tue, Oct 10, 2000 at 12:30:03PM -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 10, 2000 at 12:30:03PM -0700, Jim D. wrote: > The FIN_WAIT_2s DO eventually timeout/get cleaned up. On a 3.4-S server it > took about 4 days for > the FIN_WAITs to disappear, it was quicker on 3.5-S (about 18-24 hours?). I > still find it strange, is there > anyone that could give a detailed explanation? TCP/IP Illustrated would certainly discuss what goes on in these final states in TCP. If FreeBSD does what is listed there is another matter. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message