From owner-freebsd-net@FreeBSD.ORG Wed Jun 25 18:46:12 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77391106567A for ; Wed, 25 Jun 2008 18:46:12 +0000 (UTC) (envelope-from ali@transip.nl) Received: from relay0.transip.nl (relay0.transip.nl [80.69.67.21]) by mx1.freebsd.org (Postfix) with ESMTP id 428258FC1D for ; Wed, 25 Jun 2008 18:46:12 +0000 (UTC) (envelope-from ali@transip.nl) Received: from [192.168.0.3] (ip86-50-212-87.adsl2.static.versatel.nl [87.212.50.86]) by relay0.transip.nl (Postfix) with ESMTP id 511281032DA; Wed, 25 Jun 2008 20:27:43 +0200 (CEST) Message-ID: <48628E13.40207@transip.nl> Date: Wed, 25 Jun 2008 20:27:31 +0200 From: Ali Niknam Organization: Transip BV User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Vlad GALU References: <486283B0.3060805@transip.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: net@freebsd.org Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2008 18:46:12 -0000 > This looks like an issue we used to have at work, where a streaming > application suddenly started getting kevents for sockets that had been > already closed. While that was happening, a netstat output looked just > like yours. We never tracked it down, as we moved to other projects :( > > Was that BSD 7.0 also? -- Transip BV | http://www.transip.nl/ We never let you down.