Received: by taz.hyperreal.com (8.8.3/V2.0) id PAA27853; Wed, 8 Jan 1997 15:58:42 -0800 (PST) Received: from fully.organic.com by taz.hyperreal.com (8.8.3/V2.0) with ESMTP id PAA27841; Wed, 8 Jan 1997 15:58:36 -0800 (PST) Received: (from ed@localhost) by fully.organic.com (8.8.3/8.6.12) id XAA19643 for new-httpd@hyperreal.com; Wed, 8 Jan 1997 23:59:49 GMT From: "Ed Korthof" Message-Id: <9701081559.ZM19641@fully.organic.com> Date: Wed, 8 Jan 1997 15:59:48 -0800 In-Reply-To: "Ed Korthof" "Re: n + 1 MaxClients?" (Jan 8, 3:53pm) References: <199701082305.SAA28308@spudboy.telebase.com> <9701081553.ZM19632@fully.organic.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: new-httpd@hyperreal.com Subject: Re: n + 1 MaxClients? 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 Jan 8, 3:53pm, Ed Korthof wrote: > Subject: Re: n + 1 MaxClients? > Looking at the code, I don't think that you actually had more than > HARD_SERVER_LIMIT -- probably the a child switched from idle to busy status > while the functions counted the children were running. I should ammend that -- this holds only if you used the /status handler to get the information, as the description implied. If 'ps -ef | grep httpd | grep -v grep | wc -l' produces a number one larger than HARD_SERVER_LIMIT, that is correct (since the parent server isn't counted amoung the children). If it produces a number two larger, then there is a more serious problem and there really are more than HARD_SERVER_LIMIT children running (unless there's recently been a graceful restart, and some of the children are hanging around). That would be very bad. I attempted to reproduce it, but was unable; if you can produce that error, I'd like to know. -- -- Ed Korthof | Web Server Engineer -- -- ed@organic.com | Organic Online, Inc -- -- (415) 278-5676 | Fax: (415) 284-6891 --