in reply to Re: non-blocking backticks
in thread non-blocking backticks
But alarm sends a signal to the process that called alarm, not the child process, right? Even if it sent it to the child, the child process would need a signal handler for that process.
Maybe I wasn't clear enough in my question. The child process is not a single script, but can be a variety of scripts, and may not even be Perl. I don't want to require the child scripts be modified. Well, that was the approach I was pushing for, but my question was pertaining to changing only the parent script. How can a threaded Perl script run any system command, capture that command's output, and kill it if it runs for too long?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: non-blocking backticks
by bliako (Abbot) on Mar 26, 2019 at 23:07 UTC | |
|
Re^3: non-blocking backticks
by stevieb (Canon) on Mar 26, 2019 at 22:15 UTC |