From owner-freebsd-net@FreeBSD.ORG Thu Apr 10 00:47:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB9B437B401 for ; Thu, 10 Apr 2003 00:47:53 -0700 (PDT) Received: from corpmail.outblaze.com (202-77-223-51.outblaze.com [202.77.223.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id E13FA43F93 for ; Thu, 10 Apr 2003 00:47:50 -0700 (PDT) (envelope-from yusufg@outblaze.com) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by corpmail.outblaze.com (Postfix) with ESMTP id 95B1F7D2E for ; Thu, 10 Apr 2003 07:55:05 +0000 (GMT) Received: from yusufg.portal2.com (202-77-223-125.outblaze.com [202.77.223.125]) by corpmail.outblaze.com (Postfix) with SMTP id 6D18A520CD for ; Thu, 10 Apr 2003 07:55:05 +0000 (GMT) Received: (qmail 19534 invoked by uid 500); 10 Apr 2003 07:46:47 -0000 Date: Thu, 10 Apr 2003 15:46:47 +0800 From: Yusuf Goolamabbas To: freebsd-net@freebsd.org Message-ID: <20030410074647.GA19450@outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.6; VAE: 6.19.0.3; VDF: 6.19.0.6; host: corpmail.outblaze.com) Subject: What's the timeout value for connections in FIN_WAIT2 state X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 07:47:54 -0000 Hi, According to this page http://httpd.apache.org/docs/misc/fin_wait_2.html FreeBSD from ver 2.0 onwards has a timeout for FIN_WAIT2 state, what is the timeout for this state, is there a sysctl to control this On a loaded mailserver running 4.7-stable, I am seeing a lot of connections in FIN_WAIT2 state, and they don't seem to be going away even after 0.5 hr, other than a reboot is there any to get rid of them. My understanding is that lots of these FIN_WAIT2 states will just take up space in kernel tables Regards, Yusuf