Perrin Harkins wrote:
The difference is that Apache::Resource should apply this limit to each
new child process. When you do this from the shell, you are limiting
the parent Apache process, which isn't very useful.
I put
use BSD::Resource;
setrlimit RLIMIT_AS, 3200, 6400;
at the
hi...
I use BSD::Resource to limit the RAM a mod_perl process could get. this
works perfectly right on one machine but on another the process does not
get any RAM at all and is killed immediately. both servers run under
linux and therefor I use RLIMIT_AS as described in the mod_perl guide
from
has anybody any ideas?
Apache::Resource.
Thanx, but that leads to the same result. In the first place I used:
PerlModule Apache::Resource
PerlSetEnv PERL_RLIMIT_AS 32:64
PerlChildInitHandler Apache::Resource
in httpd.conf, but Apache::Resource uses BSD::Resource in the end and
thus its the same as
use BSD::Resource;
setrlimit
PerlModule Apache::Resource
PerlSetEnv PERL_RLIMIT_AS 32:64
PerlChildInitHandler Apache::Resource
in httpd.conf, but Apache::Resource uses BSD::Resource in the end and
thus its the same as
use BSD::Resource;
setrlimit RLIMIT_AS, 3200, 6400;
The difference is that
