Received: by taz.hyperreal.com (8.8.3/V2.0) id OAA26162; Sat, 18 Jan 1997 14:07:58 -0800 (PST) Received: from scanner.worldgate.com by taz.hyperreal.com (8.8.3/V2.0) with ESMTP id OAA26154; Sat, 18 Jan 1997 14:07:54 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id PAA15527 for new-httpd@hyperreal.com; Sat, 18 Jan 1997 15:07:54 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id PAA09103 for ; Sat, 18 Jan 1997 15:08:03 -0700 (MST) Date: Sat, 18 Jan 1997 15:08:03 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: new-httpd@hyperreal.com Subject: Re: lingering_close In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com In Solaris, you can play with tcp_fin_wait_2_flush_interval with ndd to set the timeout; not sure when they added it. If we can't fix this, we should put up a page with suggested actions and ways to get the kernel to timeout the fin_wait_2s... On Sat, 18 Jan 1997, Cliff Skolnick wrote: > > The lastest solaris (maybe earlier) will time out FIN_WAIT_2, but it > takes an hour I am told. I am getting some details from folks at sun. > > On Sat, 18 Jan 1997 rasmus@lerdorf.on.ca wrote: > > > > The other question I would ask is, "Does this OS enforce a timeout > > > for FIN_WAIT_2"? > > > > I don't know. I am seeing these on a Sparc Solaris 2.5.1 box. > > > > -Rasmus > > > > -- > Cliff Skolnick, Technical Consultant > Steam Tunnel Operations > cliff@steam.com, 415.297.5938 > http://www.steam.com/ >