From owner-freebsd-current  Mon May 19 05:04:26 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA17225
          for current-outgoing; Mon, 19 May 1997 05:04:26 -0700 (PDT)
Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA17215
          for <freebsd-current@FreeBSD.ORG>; Mon, 19 May 1997 05:04:18 -0700 (PDT)
Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.8.3/8.6.9) with SMTP id NAA01331; Mon, 19 May 1997 13:04:18 +0100 (BST)
Date: Mon, 19 May 1997 13:04:17 +0100 (BST)
From: Developer <dev@flevel.co.uk>
To: David Greenman <dg@root.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: FIN_WAIT_2 
In-Reply-To: <199705191139.EAA02861@implode.root.com>
Message-ID: <Pine.BSF.3.95q.970519130248.1321A-100000@fgate.flevel.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Mon, 19 May 1997, David Greenman wrote:

> >Does anyone know if Freebsd times out FIN_WAIT_2's.. if so what is the
> >timeout and what date was this put into the kernel?
> 
>    There have been a variety of timer changes over the past two years which
> should catch cases >= CLOSING. Specifically, the persist timer is set on
> connections >= CLOSING, so connections in FIN_WAIT_2 should be timed out by
> that timer at the very least. My vague recollection is that a different timer
> kills it before that, however.

Thanks for the information. It seems from testing on one of our machines
that the timeout may be around 5 mins. It's unfortunate that apache seems
to have no way to detect that the user has hit stop other than just
leaving the conntion in FIN_WAIT_2 until the kernel times it out.

Regards,

Trefor S.