I've been using mod_perl1 for a couple of years without problems.
I've switched to mod_perl 2 half an year ago and always have problems
(segfaults under prefork and sometimes troubles with mpm worker).
I hope that I did something wrong at compilation stage or it was
something with the system (bu
Oleg Burlaca wrote:
[...]
If this may reassure you, I have been using quite a bit of mod_perl 2 in
the last 2-3 years with Apache 2.0.x and lately 2.2.x, under Solaris,
HPUX, Linux and Windows, and have not had the kind of problems you
mention. So yes, it looks like you may have some mismatche
Thanks André
If this may reassure you, I have been using quite a bit of mod_perl 2
in the last 2-3 years with Apache 2.0.x and lately 2.2.x, under
Solaris, HPUX, Linux and Windows, and have not had the kind of
problems you mention. So yes, it looks like you may have some
mismatched stuff ther
Oleg Burlaca wrote:
and one more question: I have read that on linux platforms it's better
to use prefork instead of mpm-worker, I remember that we did some
performance test ourselves and it sounds to be true.
prefork will use a different process for each Apache child and thus a
different Pe
Michael Peters wrote:
prefork will use a different process for each Apache child and thus a
different Perl interpreter for each process. Normally this would mean
a lot of memory usage, but since Linux uses COW (copy-on-write) memory
as long as you preload you'll actually see about the same memo
Hi, just got a fresh VPS server and wanted to install the second apache
on 8080 but without success
The configure process was ok, with only one warning:
Your Perl is configured to link against libgdbm,
but libgdbm.so was not found.
You could just symlink it to /usr/lib/libgdbm.so.2.0.0
perl Ma
