d'origine-
De : Grant [mailto:[EMAIL PROTECTED]
Envoyé : dimanche 30 septembre 2007 00:35
À : users@httpd.apache.org
Objet : Re: [EMAIL PROTECTED] 127.0.0.1 access_log errors
Ok, thanks Joshua. Do these entries indicate that I might need to
make a change in my prefork settings? I'm
I've been getting many errors like this in ssl_access_log:
127.0.0.1 - - [28/Sep/2007:09:07:29 -0700] GET / - - 400 470
and now access_log has started printing these:
127.0.0.1 - - [28/Sep/2007:03:10:07 -0700] GET / HTTP/1.0 404 24 -
Apache (internal dummy connection)
I read here:
On 9/29/07, Grant [EMAIL PROTECTED] wrote:
I've been getting many errors like this in ssl_access_log:
127.0.0.1 - - [28/Sep/2007:09:07:29 -0700] GET / - - 400 470
and now access_log has started printing these:
127.0.0.1 - - [28/Sep/2007:03:10:07 -0700] GET / HTTP/1.0 404 24 -
Apache
On 9/29/07, Grant [EMAIL PROTECTED] wrote:
Ok, thanks Joshua. Do these entries indicate that I might need to
make a change in my prefork settings? I'm currently using:
StartServers10
MinSpareServers 10
MaxSpareServers 20
MaxClients 256
Ok, thanks Joshua. Do these entries indicate that I might need to
make a change in my prefork settings? I'm currently using:
StartServers10
MinSpareServers 10
MaxSpareServers 20
MaxClients 256
MaxRequestsPerChild 100
No, those log
Grant wrote:
Ok, would you use 0? I was concerned about a process going haywire
eventually.
Whoa - there's zero reason to use MaxRequestsPerChild unless you encounter
a specific resource allocation/unbounded utilization flaw in a specific (or
mystery) module you've loaded.
In nearly ever
