From test-dev-return-2849-apmail-httpd-test-dev-archive=httpd.apache.org@httpd.apache.org Wed Apr 28 12:27:20 2004 Return-Path: Delivered-To: apmail-httpd-test-dev-archive@www.apache.org Received: (qmail 14213 invoked from network); 28 Apr 2004 12:27:19 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 28 Apr 2004 12:27:19 -0000 Received: (qmail 18108 invoked by uid 500); 28 Apr 2004 12:27:17 -0000 Delivered-To: apmail-httpd-test-dev-archive@httpd.apache.org Received: (qmail 18020 invoked by uid 500); 28 Apr 2004 12:27:16 -0000 Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: test-dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list test-dev@httpd.apache.org Received: (qmail 18005 invoked from network); 28 Apr 2004 12:27:16 -0000 Received: from unknown (HELO secure.exclamationlabs.net) (66.77.29.182) by daedalus.apache.org with SMTP; 28 Apr 2004 12:27:16 -0000 Received: from modperlcookbook.org (pcp05682390pcs.walngs01.pa.comcast.net [69.139.166.203]) (authenticated (0 bits)) by secure.exclamationlabs.net (8.11.6/8.11.6) with ESMTP id i3SCRHI21354 for ; Wed, 28 Apr 2004 07:27:17 -0500 Message-ID: <408FA2FE.2060801@modperlcookbook.org> Date: Wed, 28 Apr 2004 08:26:38 -0400 From: Geoffrey Young User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 X-Accept-Language: en-us, en MIME-Version: 1.0 To: test-dev@httpd.apache.org Subject: Re: getting rid of 'server reached MaxClients setting' error References: <408D8F07.6020408@stason.org> In-Reply-To: <408D8F07.6020408@stason.org> X-Enigmail-Version: 0.83.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Stas Bekman wrote: > I think this misleading error is really a bug in Apache: > > [Mon Apr 26 15:28:44 2004] [error] server reached MaxClients setting, > consider raising the MaxClients setting > It sounds like a one-off bug to me. the only issue I see is that now both 1.0 and 2.0 environments two servers by default instead of one, which seems noteworthy I guess. I can't see the harm, but when I changed from httpd -X to StartServers 1 I did so with trepidation. at the very least I think we should support a way to get back to a single server if users desire it. -minclients=0 (so maxclients = minclients + 1 = 1) not only isn't intuitive, but it doesn't look to be supported in the code. maybe a -singleserver option is worth adding, which would effectively restore everything you propose to undo here? maybe just calling t_server_log_is_expected() early on is a better idea (if it's even possible)? --Geoff