Re^3: How to be a child of IPC::Run?

Responding to my own post is so awfully tacky, but if I add this before my for loop in wr2, my example works:

$| = 1;
[download]

Now I'll see if I can figure out the rest.

Comment on Re^3: How to be a child of IPC::Run? Download Code

Replies are listed 'Best First'.
Re^4: How to be a child of IPC::Run? by cwood (Initiate) on May 02, 2012 at 09:30 UTC
Finally, I kept getting "process ended prematurely at /home/cwood/bin/pr2 line 46" in my more involved work elsewhere. I printed the parent's output (child's input) at the parent, and that helped me discover a stray "exit 0" leftover from when my child was a script forked with each execution. Similarly a "print 123" without the "\n" would have caused an apparent IPC freeze if I was checking for /\n/ in the parent's input (child's output). So two answers: unbuffered output on the child watch for leftovers from previous techniques on parent and child	[reply]

Replies are listed 'Best First'.

Re^4: How to be a child of IPC::Run?
by cwood (Initiate) on May 02, 2012 at 09:30 UTC

Finally, I kept getting "process ended prematurely at /home/cwood/bin/pr2 line 46" in my more involved work elsewhere. I printed the parent's output (child's input) at the parent, and that helped me discover a stray "exit 0" leftover from when my child was a script forked with each execution.

Similarly a "print 123" without the "\n" would have caused an apparent IPC freeze if I was checking for /\n/ in the parent's input (child's output).

So two answers:

unbuffered output on the child
watch for leftovers from previous techniques on parent and child

[reply]