[EMAIL PROTECTED] wrote:
NetBSD-2.0_RC1 + perl-5.8.5 + httpd-2.0.52 :
all the above builds and runs OK, but
when trying to configure source of modperl-1.99_17-dev I get the
following:
$ perl Makefile.PL MP_AP_PREFIX=$HOME/mp-test/httpd-2.0
Reading Makefile.PL args from @ARGV
MP_AP_PREFIX = /ho
[EMAIL PROTECTED] wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
test server didn't start (t/logs/error_log):
Leo, have you by chance read the suggestion that was printed out when
'make test' has aborted. Please try again and do exactly what it s
Torsten Förtsch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 30 September 2004 19:48, Alex Greg wrote:
Thanks for your response. Sorry I wasn't clear; the httpd processes
don't actually kill the server, they just slow Apache right down to the
point at which it doesn't respond to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 30 September 2004 19:48, Alex Greg wrote:
> Thanks for your response. Sorry I wasn't clear; the httpd processes
> don't actually kill the server, they just slow Apache right down to the
> point at which it doesn't respond to requests any mo
Ken Miller <[EMAIL PROTECTED]> writes:
[...]
> So, what's the solution to this?
Consider upgrading to libapreq2/mp2, or use Apache::args() instead
of Apache::Request::args(). The code in question *might* work with
libapreq1 if you replace $r->args with $r->SUPER::args, but I'm
not sure.
--
Jo
Geoffrey Young wrote:
Alex Greg wrote:
Hi,
[...]
[Thu Sep 30 09:44:43 2004] [error] (12)Cannot allocate memory: fork:
Unable to fork new process
there is lots of documentation around about how to tune your httpd processes
so that they don't kill your box. see, for example
http://perl.apache.org
Alex Greg wrote:
> Hi,
>
>
> We've been having some issues with our mod_perl web servers recently.
> Basically what happens is the server becomes very very slow, to the
> point of being almost totally unresponsive. At the time this happens, we
> see this in the error log:
>
>
> [Thu Sep 30 09
Hi,
We've been having some issues with our mod_perl web servers recently.
Basically what happens is the server becomes very very slow, to the
point of being almost totally unresponsive. At the time this happens, we
see this in the error log:
[Thu Sep 30 09:44:43 2004] [error] (12)Cannot allocat