Received: (from majordom@localhost) by hyperreal.com (8.8.4/8.8.4) id RAA21090; Sun, 6 Apr 1997 17:59:42 -0700 (PDT) Received: from bilge-gw.topsail.org (bilge-gw.topsail.org [207.8.162.150]) by hyperreal.com (8.8.4/8.8.4) with ESMTP id RAA21069 for ; Sun, 6 Apr 1997 17:59:38 -0700 (PDT) Received: from argo.topsail.org ([172.16.86.5]) by bilge-gw.topsail.org (8.8.5/8.7.3) with ESMTP id UAA04542 for ; Sun, 6 Apr 1997 20:59:35 -0400 (EDT) Message-ID: <334846F6.24E6B93F@topsail.org> Date: Sun, 06 Apr 1997 20:59:34 -0400 From: Chuck Murcko Organization: The Topsail Group X-Mailer: Mozilla 4.0b3C (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: [PATCH] Last lingering cleanup, setsockopt error messages X-Priority: 3 (Normal) References: <9704060709.aa21292@paris.ics.uci.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Roy T. Fielding wrote: > > I've gone through all the lingering_close stuff again and found > a few areas where things can now be cleaned up, better documented, > and coded in a less disorienting fashion. I found that the nonblocking > stuff is not needed after all, the error messages are never useful, > and the timeout needed to be specialized to avoid double-logging. > I also fixed the error messages for the setsockopt options, and > removed one case where sock_disable_nagle was being called for no > good reason. Also added Unixware, NeXT, and Irix to the NO_LINGCLOSE > list, mostly in conf.h if there is a -D for it. > Work fine here. +1. -- chuck Chuck Murcko The Topsail Group, West Chester PA USA chuck@topsail.org