On Mon, 17 Jan 2000, Bill Moseley wrote:
> The httpd.conf Timeout setting doesn't effect mod_perl, it seems, even if
> the client breaks the connection.
>
> Is there a recommendation on how to catch & stop run away mod_perl programs
> in a way that's _not_ part of the run away program. Or is this even
> possible? Some type of watchdog, just like httpd.conf Timeout?
how is it 'running away' exactly? any insight with strace or gdb? as of
1.3.6, scripts should be able to continue on after the connection is
broken and apache i/o functions become noops (they don't bother trying to
write to the socket). does it help if you add to httpd.conf:
PerlFixupHandler Apache::SIG
?
