Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 17754 invoked by uid 6000); 26 Jan 1999 17:45:08 -0000 Received: (qmail 17740 invoked from network); 26 Jan 1999 17:45:06 -0000 Received: from ha1.rdc1.bc.wave.home.com (HELO mail.rdc1.bc.wave.home.com) (imail@24.2.10.66) by taz.hyperreal.org with SMTP; 26 Jan 1999 17:45:06 -0000 Received: from cr373760-a ([24.112.120.112]) by mail.rdc1.bc.wave.home.com (InterMail v4.00.03 201-229-104) with SMTP id <19990126174505.BOCA7852.mail.rdc1.bc.wave.home.com@cr373760-a> for ; Tue, 26 Jan 1999 09:45:05 -0800 Message-ID: <005e01be4953$847d4cf0$70787018@cr373760-a.nvcr1.bc.wave.home.com> From: "Vincent Janelle" To: Subject: Re: Multi-threaded apache rather than pre-forking Date: Tue, 26 Jan 1999 09:44:26 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Is there some better documentation for things to check? Themes.org got *loaded* because of apache and some "misconfiguration", however, I had to take some rather drastic measures in order to stop the machine from dying(I'm looking into that, I think it was a libc problem). Sorry if this isn't the place to ask, however, it is an issue that I think apache suffers from.. The words "not" and "scalable" often apply to things like this when a different webserver handles it with one configuration change... >If a machine isn't configured for high traffic, it can't handle high >traffic. It isn't just the webserver involved. >