From owner-freebsd-hackers  Mon Jun 14  0:37:38 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 6866B15255
	for <hackers@FreeBSD.ORG>; Mon, 14 Jun 1999 00:37:36 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id AAA07041;
	Mon, 14 Jun 1999 00:37:28 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 14 Jun 1999 00:37:28 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199906140737.AAA07041@apollo.backplane.com>
To: Dan Moschuk <dan@trinsec.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: hundreds of sockets stuck in TIME_WAIT
References:  <19990609115951.A79834@trinsec.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:I noticed on a very high traffic'd webserver, I have just over 4000 sockets
:stuck in the TIME_WAIT state.  Ideally, I want to "bend" the RFC a bit and
:close the descriptor before it hits that state, or, ignore the 2MSL wait
:when it enters that state.  
:
:I take it there is no sysctl switch to trigger this, so, am I going 
:kernel diving?
:
:-Dan

    Just ignore them, that's what we do.  They should not start to
    impact on performance until you hit at least 15000 sockets.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message