From owner-freebsd-current  Mon May 19 04:38:08 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA16001
          for current-outgoing; Mon, 19 May 1997 04:38:08 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA15996
          for <freebsd-current@FreeBSD.ORG>; Mon, 19 May 1997 04:38:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with SMTP id EAA02861;
	Mon, 19 May 1997 04:39:26 -0700 (PDT)
Message-Id: <199705191139.EAA02861@implode.root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: Developer <dev@flevel.co.uk>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: FIN_WAIT_2 
In-reply-to: Your message of "Mon, 19 May 1997 11:43:29 BST."
             <Pine.BSF.3.95q.970519114250.2842A-100000@fgate.flevel.co.uk> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 19 May 1997 04:39:26 -0700
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>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.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project