On Sun, 15 Jun 2008 21:09:23 -0500
Michael Gardner <[EMAIL PROTECTED]> wrote:
> Workarounds would be helpful, but naturally I'd prefer to eliminate
> the cause of the problem. I've been looking through the
> documentation, but haven't made much progress so far. How can I get
> to the bottom of this?
Most likely there is some bad Perl in there that is slurping in
large amounts of data or a possible memory leak.
An fairly easy work around is to reduce MaxRequestsPerChild to
a fairly low level say like 20 so that any children that grow
large will be reaped more quickly.
-------------------------------------------------------
Frank Wiles, Revolution Systems, LLC.
Personal : [EMAIL PROTECTED] http://www.wiles.org
Work : [EMAIL PROTECTED] http://www.revsys.com
