Hi all,
I searched for that solution for hours not finding any until
Torsten posted this one.
IMHO it's worth it to put Torsten's snippet to the documentation
pages of mod_perl.
Even the book 'mod_perl 2 user's guide' leaves a big hole
in that area.
Thank you Torsten!
Best regards
Andreas Mock
Torsten Förtsch wrote on 2010-03-11:
> On Thursday 11 March 2010 15:18:08 Steve Hay wrote:
>> I have a mod_perl-2 handler that uses custom_response() to display
>> error messages if something goes wrong:
>>
>> $r->custom_response(Apache2::Const::SERVER_ERROR, $error);
>> return Apache2::Const::SER
Am 11.03.2010 um 22:41 schrieb ARTHUR GOLDBERG:
> Running Perl programs in mod_perl in Apache (2.2) on RHEL:
>
>> [10 a...@virtualplant:/etc]$ cat /etc/redhat-release
>> Red Hat Enterprise Linux Server release 5.4 (Tikanga)
>> [11 a...@virtualplant:/etc]$ uname -r
>> 2.6.18-164.11.1.el5
> Occasi
On Thu, Mar 11, 2010 at 1:41 PM, ARTHUR GOLDBERG wrote:
>
> OK, that kills big processes. What happens next is that Perl runs out of
> memory (outputs "Out of Memory!") and calls the __DIE__ signal handler. So,
> my plan is to catch the signal, redirect the browser to an error page, and
> finally
