APACHE 2.3 STATUS: -*-text-*-
Last modified at [$Date: 2006-08-22 16:41:03 -0400 (Tue, 22 Aug 2006) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
Documentation status is maintained se
APACHE 2.2 STATUS: -*-text-*-
Last modified at [$Date: 2007-06-01 13:31:49 -0400 (Fri, 01 Jun 2007) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS
Documentation status is main
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2007-05-08 19:18:57 -0400 (Tue, 08 May 2007) $]
The current version of this file can be found at:
* http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/STATUS
Documentation status is main
It looks the the 1.3 pid_table impl is pretty much on target.
I've been testing the trunk (2.3.x) version with no issues that
I've been able to see, but was wondering how many others
are testing...
In the meantime, should I create a 2.2 branch for the 2.2-version
of the pid_table code and backpor
The directives:
MaxClients 512
ServerLimit512
in that order results in
WARNING: MaxClients of 512 exceeds ServerLimit value of 256 servers,
lowering MaxClients to 256. To increase, please see the ServerLimit
directive.
Reversing the directives fixes the problem.
I h
In general you should use Apache 2.2 instead of Apache 2.0 if possible,
especially if you are building for 64 bit. As far as I remember Apache 2.0
has some problems with 64 bit (I do not remember the details now).
Apache 2.2 works smoothly with 64 bit, but on Linux you might be hit
by an apr-util i
