Hi,
I have a perl script running in mod_perl that needs to write a large amount of
data to the client, possibly over a long period. The behavior that I observe is
that once I print and flush something, the buffer memory is not reclaimed even
though I rflush (I know this cant be reclaimed back b
Thanks Perrin
Unfortunately, this doesn't work.
First, failure of a mod_perl process with "Out of Memory!", as occurs
when the softlimit of RLIMIT_AS is exceeded, does not trigger an Apache
ErrorDocument 500. A mod_perl process that exits (actually CORE::exit()
must be called), that doesn't tri
On Sun, Mar 14, 2010 at 11:22 AM, Arthur Goldberg wrote:
> Perhaps you're referring to Apache's ErrorDocument (also described in Custom
> Error Response).
Yes, that's what I meant.
> While that can run local Perl (in a new process of course)
> as in the example
> ErrorDocument 500 /cgi-bi
Hi,
driven by Andreas Mock who wanted my "custom_response/content-type" snippet in
the docs and by Tosh Cooey who wanted my "spawning off long running processes"
method to be callable without thinking I did a bit of writing over the
weekend.
Some of you might find it interesting, I hope.
http
