Received: by taz.hyperreal.com (8.8.3/V2.0) id WAA10297; Mon, 30 Dec 1996 22:17:13 -0800 (PST) Received: from scanner.worldgate.com by taz.hyperreal.com (8.8.3/V2.0) with ESMTP id WAA10293; Mon, 30 Dec 1996 22:17:07 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id XAA09522 for new-httpd@hyperreal.com; Mon, 30 Dec 1996 23:17:04 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id XAA09659 for ; Mon, 30 Dec 1996 23:17:03 -0700 (MST) Date: Mon, 30 Dec 1996 23:17:02 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: new-httpd@hyperreal.com Subject: comment on HARD_SERVER_LIMIT in httpd.h 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 src/httpd.h still reads: /* Limit on the total --- clients will be locked out if more servers than * this are needed. It is intended solely to keep the server from crashing * when things get out of hand. * * We keep a hard maximum number of servers, for two reasons --- first off, * in case something goes seriously wrong, we want to stop the fork bomb * short of actually crashing the machine we're running on by filling some * kernel table (I was originally going to make this 256, but it turns out * that that would actually fill the process table on reasonably configured * machines). Secondly, it keeps the size of the scoreboard file small * enough that we can read the whole thing without worrying too much about * the overhead. */ #define HARD_SERVER_LIMIT 256 HARD_SERVER_LIMIT was bumped up a while ago, but the note about it not being 256 wasn't removed/modified.