};
if ( $@ ) {
alarm 0; # just in case wasn't a timeout that died
[...]
}
I mentioned this yesterday: One interesting item is that the "exit signal
Alarm Clock (14)" is almost always 5 minutes and two or three seconds after
the last completed mod_perl request.
Still still trying to figure this out:
I get about 10 or 20 exit signal Alarm Clock (14) messages a day -- out of
15,000+ requests. Not very many.
I log the PID of my mod_perl script each request, and for each 'exit signal
Alarm Clock (14)' there seems to be a mod_perl request about
At 04:34 PM 02/09/00 +0200, Stas Bekman wrote:
>> eval {
>> local $SIG{__DIE__};
>> local $SIG{ALRM} = CORE::sub { die "Timeout" };
>
>Anonymous sub within package CORE? I've never seen such a code...
Oh, that's some old code that I just still use. I assumed it's harmless.
The problem w
> Apache/1.3.9 (Unix) mod_perl/1.21 perl 5.005_03
>
> [notice] child pid 16903 exit signal Alarm Clock (14)
>
> I'm confused by this one. I was thinking that this was the case of:
> http://perl.apache.org/guide/debug.html#Handling_the_server_timeout_case
>
> Whic
Apache/1.3.9 (Unix) mod_perl/1.21 perl 5.005_03
[notice] child pid 16903 exit signal Alarm Clock (14)
I'm confused by this one. I was thinking that this was the case of:
http://perl.apache.org/guide/debug.html#Handling_the_server_timeout_case
Which I though was fixed for $SIG{ALRM}
