|Subject:||Clarify effect on child processes|
Thanks for your module Timeout::Self, which has proven really useful in our unittests to assure that the CI jobs get finished, even if some bug results in an endless loop. One thing we noticed however is that it doesn't play perfectly nice with programs that fork: While the alarm handler gets cloned to the child process by Perl, the alarm is not set again - so the child process will not time out. While this is of course not Timeout::Self's fault, it would be great if you could either document this fact in the POD, or decide to do something about it: one option is to useto re-set the alarm on the forked process... Thanks!