Received: by taz.hyperreal.com (8.8.3/V2.0) id LAA26573; Tue, 14 Jan 1997 11:51:05 -0800 (PST) Received: from scanner.worldgate.com by taz.hyperreal.com (8.8.3/V2.0) with ESMTP id LAA26560; Tue, 14 Jan 1997 11:51:01 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id MAA25685 for new-httpd@hyperreal.com; Tue, 14 Jan 1997 12:50:59 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id MAA22210 for ; Tue, 14 Jan 1997 12:38:36 -0700 (MST) Date: Tue, 14 Jan 1997 12:38:35 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: new-httpd@hyperreal.com Subject: Re: lingering_close In-Reply-To: <199701141813.MAA20720@sierra.zyzzyva.com> 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 On Tue, 14 Jan 1997, Randy Terbush wrote: > We currently _aren't_ calling lingering_close() in timeout(). > I'm of the opinion that we should be. We call blclose() which > is closing the socket. We then longjump back to child_main() > where I _think_ that we are calling lingering_close() which > leads to the "Invalid argument" error coming from the error > code I added to the first shutdown() call in lingering_close(). I can't comment on where what is being done and where what should be done since I don't have the time to look through the code right now, but I iff NO_LINGCLOSE helps, then the problem is not likely to be due to not using lingering_close() in timeout() because we didn't do that before because it didn't exist before and it did work fine for people that are now haveing problems. That doesn't necessarily mean what we are doing now is right or shouldn't be changed. Keep in mind that we may be seeing multiple problems here, since some don't seem to be helped by NO_LINGCLOSE.