This isn't really what I meant. Or how would you adapt this in any elegant way so that when put in a.sh, it runs the code in the script itself under a new process group? (The idea being that you could say my $x=`./a.sh` without creating an extra wrapper script.)
In reply to Re^5: parent process stuck in read(2) on pipe opened to child process using backtick
by Eliya
in thread parent process stuck in read(2) on pipe opened to child process using backtick
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |