Return-Path: Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org Received: (qmail 74907 invoked by uid 500); 23 Apr 2003 19:40:53 -0000 Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list cvs@httpd.apache.org Received: (qmail 74868 invoked by uid 500); 23 Apr 2003 19:40:53 -0000 Delivered-To: apmail-httpd-2.0-cvs@apache.org Date: 23 Apr 2003 19:40:52 -0000 Message-ID: <20030423194052.6836.qmail@icarus.apache.org> From: nd@apache.org To: httpd-2.0-cvs@apache.org Subject: cvs commit: httpd-2.0/docs/manual/mod worker.html.en worker.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N nd 2003/04/23 12:40:52 Modified: docs/manual/mod Tag: APACHE_2_0_BRANCH worker.html.en worker.xml Log: keep consistent with 2.1 Revision Changes Path No revision No revision 1.15.2.4 +1 -1 httpd-2.0/docs/manual/mod/worker.html.en Index: worker.html.en =================================================================== RCS file: /home/cvs/httpd-2.0/docs/manual/mod/worker.html.en,v retrieving revision 1.15.2.3 retrieving revision 1.15.2.4 diff -u -r1.15.2.3 -r1.15.2.4 --- worker.html.en 30 Mar 2003 03:14:17 -0000 1.15.2.3 +++ worker.html.en 23 Apr 2003 19:40:52 -0000 1.15.2.4 @@ -36,7 +36,7 @@

The most important directives used to control this MPM are ThreadsPerChild, which - controls the number of threads deployed by each child process, and + controls the number of threads deployed by each child process and MaxClients, which controls the maximum total number of threads that may be launched.

1.8.2.4 +1 -1 httpd-2.0/docs/manual/mod/worker.xml Index: worker.xml =================================================================== RCS file: /home/cvs/httpd-2.0/docs/manual/mod/worker.xml,v retrieving revision 1.8.2.3 retrieving revision 1.8.2.4 diff -u -r1.8.2.3 -r1.8.2.4 --- worker.xml 15 Apr 2003 22:56:41 -0000 1.8.2.3 +++ worker.xml 23 Apr 2003 19:40:52 -0000 1.8.2.4 @@ -19,7 +19,7 @@

The most important directives used to control this MPM are ThreadsPerChild, which - controls the number of threads deployed by each child process, and + controls the number of threads deployed by each child process and MaxClients, which controls the maximum total number of threads that may be launched.