Here's a possibly relevant note in the docs for both "alarm" and "sleep":
It is usually a mistake to intermix "alarm" and "sleep" calls, because "sleep" may be internally implemented on your system with "alarm". On Tue, Oct 4, 2016 at 1:34 PM, Chas. Owens <chas.ow...@gmail.com> wrote: > The first alarm is in a different process (same PID different process) due > to the exec. I am not sure what is happening, but in general it is never a > good idea to do anything complex in a signal handler. > > On Tue, Oct 4, 2016 at 4:21 PM Shawn H Corey <shawnhco...@nili.ca> wrote: >> >> On Tue, 04 Oct 2016 19:32:44 +0000 >> "Chas. Owens" <chas.ow...@gmail.com> wrote: >> >> > It looks like the problem exists at the C level as well. This code >> > doesn't work past the first alarm: >> >> Doesn't it say the alarm has to be reset by the code in the >> documentation? After all, you don't want a second alarm to go off >> before the first handler is finished. If it did, there's a chance of an >> infinite number of alarms to stack up, fill memory, and kill the >> process. >> >> >> -- >> Don't stop where the ink does. >> >> Shawn H Corey >> mailto:shawnhco...@nili.ca >> >> -- >> To unsubscribe, e-mail: beginners-unsubscr...@perl.org >> For additional commands, e-mail: beginners-h...@perl.org >> http://learn.perl.org/ >> >> > -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/