From owner-freebsd-questions Tue Jun 2 12:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20682 for freebsd-questions-outgoing; Tue, 2 Jun 1998 12:05:45 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mailwall.nwest.mccaw.com (mailwall.attws.com [155.176.34.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20669 for ; Tue, 2 Jun 1998 12:05:35 -0700 (PDT) (envelope-from jaxley@invernes.nwest.attws.com) Received: from viruswall.entp.attws.com by mailwall.nwest.mccaw.com (8.8.8/AT&T Wireless Services, Inc. V8 version 2) id MAA20948; Tue, 2 Jun 1998 12:05:03 -0700 (PDT) Received: from nwestmail.nwest.mccaw.com by viruswall.entp.attws.com (8.8.8/AT&T Wireless Services, Inc. V8 version 2) id MAA18002; Tue, 2 Jun 1998 12:05:02 -0700 (PDT) Received: by nwestmail.nwest.mccaw.com (8.6.12/McCaw V8 version 1) id MAA18502; Tue, 2 Jun 1998 12:05:01 -0700 Received: from invernes.nwest.attws.com by nwestmail.nwest.mccaw.com (8.6.12/McCaw V8 version 1) id MAA18496; Tue, 2 Jun 1998 12:05:00 -0700 Received: from invernes.nwest.mccaw.com (dorf [141.204.9.84]) by invernes.nwest.attws.com (8.8.8/8.8.8) with ESMTP id MAA15227; Tue, 2 Jun 1998 12:04:45 -0700 (PDT) Message-Id: <199806021904.MAA15227@invernes.nwest.attws.com> Date: Tue, 2 Jun 1998 12:04:53 -0700 (PDT) From: jason.axley@attws.com Subject: Re: closing TIME_WAIT connections??? To: andrew@iaccess.com.au cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <00f401bd8db4$b75877e0$e34a05cb@alpine.iaccess> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG These aren't connections that are still open, they have been closed but the local TCP sockets are in the TIME_WAIT state. This is a feature of TCP implementations that keeps another application from opening the same port too soon and possibly receiving packets that were destined for the application that *used* to be connected to that port. The length of time it takes for these to time out is TCP implementation dependent and is usually around 2 minutes. They are nothing to worry about! The netstat manpage probably describes what the text in that column means. Here's the entry from the Solaris netstat manpage: TIME_WAIT Wait after close for remote shut- down retransmission. -Jason On 2 Jun, Andrew Specht wrote: > Hi, > > Is there a way to decrease the time connections stay open? > > For example, this is what i get with netstat -an: > > tcp 0 0 222.5.45.8.8080 TIME_WAIT > tcp 0 0 127.0.0.1.81 TIME_WAIT > tcp 0 0 222.5.45.8.8080 TIME_WAIT > tcp 0 0 127.0.0.1.81 TIME_WAIT > tcp 0 0 222.5.45.8.8080 TIME_WAIT > tcp 0 0 127.0.0.1.81 TIME_WAIT > tcp 0 0 127.0.0.1.81 TIME_WAIT > tcp 0 0 222.5.45.8.8080 TIME_WAIT > tcp 0 0 222.5.45.8.8080 TIME_WAIT > tcp 0 0 127.0.0.1.81 TIME_WAIT > tcp 0 0 222.5.45.8.8080 TIME_WAIT > tcp 0 0 127.0.0.1.81 TIME_WAIT > tcp 0 0 222.5.45.8.8080 TIME_WAIT > > There are hundreds of connections like that.. > > Is there a way to close these after a specific amount of time, maybe in the > kernel source? > > Thanks again > > > > Andrew Specht | System > Administrator > E-mail: andrew@iaccess.com.au | Internet Access Australia > Internet: http://www.iaccess.com.au | Melbourne, Australia > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- -Jason +-------------------------------------------------------------------------+ | Jason Axley jason.axley@attws.com | | System Administrator Phone: 425-828-8473 | | AT&T Wireless Services Fax: 425-828-1720 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message