Received: by taz.hyperreal.com (8.8.4/V2.0) id IAA12181; Sat, 1 Feb 1997 08:22:28 -0800 (PST) Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.8.4/V2.0) with ESMTP id IAA12175; Sat, 1 Feb 1997 08:22:13 -0800 (PST) Received: from sierra (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.8.4/8.8.2) with ESMTP id KAA07663 for ; Sat, 1 Feb 1997 10:29:34 -0600 (CST) Message-Id: <199702011629.KAA07663@sierra.zyzzyva.com> To: new-httpd@hyperreal.com Subject: Re: FIN_WAIT_2 In-reply-to: jim's message of Sat, 01 Feb 1997 09:40:16 -0500. <199702011440.JAA01151@shado.jaguNET.com> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Feb 1997 10:29:34 -0600 From: Randy Terbush Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com FTR - I'm not convinced we have found the solution here either. My sky has been falling in some other areas and I have not had much time to offer constructive data or suggestions. One fact remains that we are calling shutdown on closed sockets. Dunno if this is a symptom or just a fact of life. > Ok, ok.... I'll be quiet... > > It's kinda obvious that no one else seems as concerned about those > OSs without FIN_WAIT_2 timeouts. I seem to be bugging people too > much as well... > > I'll be a good boy now :) > > -- > ==================================================================== > Jim Jagielski | jaguNET Access Services > jim@jaguNET.com | http://www.jaguNET.com/ > "Not the Craw... the CRAW!"