From owner-freebsd-questions@FreeBSD.ORG Fri Jan 25 18:41:37 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2C3216A421 for ; Fri, 25 Jan 2008 18:41:37 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id D420913C4D3 for ; Fri, 25 Jan 2008 18:41:37 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id B16542010039; Fri, 25 Jan 2008 10:41:37 -0800 (PST) Received: from relay13.apple.com (unknown [127.0.0.1]) by relay13.apple.com (Symantec Mail Security) with ESMTP id 9A0BB28094; Fri, 25 Jan 2008 10:41:37 -0800 (PST) X-AuditID: 1180711d-9dbeebb000001e9b-af-479a2d6124d1 Received: from cswiger1.apple.com (cswiger1.apple.com [17.214.13.96]) by relay13.apple.com (Apple SCV relay) with ESMTP id 877D72808C; Fri, 25 Jan 2008 10:41:37 -0800 (PST) Message-Id: <8EE034DE-AB49-4E93-B796-8D8B70E3D6FD@mac.com> From: Chuck Swiger To: Tge B In-Reply-To: <83fad2cc0801250937j21345911v3ab98110958ca335@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Fri, 25 Jan 2008 10:41:36 -0800 References: <83fad2cc0801250937j21345911v3ab98110958ca335@mail.gmail.com> X-Mailer: Apple Mail (2.915) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-questions@freebsd.org Subject: Re: Bizarre TIME_WAIT socket buildup problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 18:41:38 -0000 On Jan 25, 2008, at 9:37 AM, Tge B wrote: > On FreeBSD 6.0-RELEASE (GENERIC i386), I am experiencing a rather > worrying > situation: connections to some ports (namely, 80 and > 25) end up in a TIME_WAIT state - normal - but none have been removed > in the last 24 hours. My net.inet.tcp.msl was set to the default > 30000, > a few hours ago I changed it to 5000 to no avail - all new connections > end up in the TIME_WAIT line, at the bottom of which are connections > from almost 24 hours ago that have been in the TIME_WAIT state ever > since. I believe there was bug there which has been fixed in later 6.x releases; please try upgrading to 6.3. -- -Chuck