Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 8461 invoked by uid 6000); 11 Jul 1999 16:46:55 -0000 Received: (qmail 8455 invoked from network); 11 Jul 1999 16:46:53 -0000 Received: from out4.ibm.net (165.87.194.239) by taz.hyperreal.org with SMTP; 11 Jul 1999 16:46:53 -0000 Received: from lig32-227-32-44.us.lig-dial.ibm.com (slip-32-101-164-162.nc.us.ibm.net [32.101.164.162]) by out4.ibm.net (8.8.5/8.6.9) with ESMTP id QAA25080 for ; Sun, 11 Jul 1999 16:46:51 GMT Date: Sun, 11 Jul 1999 12:46:51 -0400 (Eastern Daylight Time) From: Rasmus Lerdorf To: "new-httpd@apache.org" Subject: Re: newbie thread/process model question in hybrid server In-Reply-To: <199907111425.AAA31743@silk.apana.org.au> Message-ID: X-X-Sender: rasmus@imap3.bellglobal.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Status: O > >But how do you know? If you can't be sure that no memory corruption has > >taken place, then continuing is completely invalid, as far as I am > >concerned. > > Can you ever be sure your memory isn't corrupted? Not all corruption causes a > segfault. I suppose, but a seg fault is a pretty good clue that someone wrote somewhere in memory that they shouldn't have. Not that I really care, I don't use OS/2, I'd just hate to see this sort of approach in any production server I run. -Rasmus