Re: Capturing file descriptor 3, or alternatives.

2012-06-25 Thread Kevin D. Clark
I've thought about this problem during my commute for a week now, and I haven't been able to come up with a simple solution that satisfies the constraints. I think that a lot of effort could be put into solving this problem with these constraints...or...the problem could be solved simply with a

Obtaining user input via interactive child proc

2012-06-25 Thread Michael ODonnell
I've thought about this problem during my commute for a week now, and I haven't been able to come up with a simple solution that satisfies the constraints. It's an interesting puzzle. You mention constraints but we don't really have a clear problem statement. [...] the problem could be

Re: Capturing file descriptor 3, or alternatives.

2012-06-25 Thread Ben Scott
On Mon, Jun 25, 2012 at 9:13 AM, Kevin D. Clark kevin_d_cl...@comcast.net wrote: I think that a lot of effort could be put into solving this problem with these constraints...or...the problem could be solved simply with a small temporary file that parent+child agreed to use. ... I'm a big fan

Re: Capturing file descriptor 3, or alternatives.

2012-06-25 Thread Joshua Judson Rosen
Ben Scott dragonh...@gmail.com writes: On Mon, Jun 25, 2012 at 9:13 AM, Kevin D. Clark kevin_d_cl...@comcast.net wrote: I think that a lot of effort could be put into solving this problem with these constraints...or...the problem could be solved simply with a small temporary file that

SOLVED: Capturing file descriptor 3, or alternatives.

2012-06-25 Thread Ben Scott
On Tue, Jun 19, 2012 at 4:34 PM, Bill Freeman ke1g...@gmail.com wrote: What occurred to me is to send the final result to fd 3, which the shell would have to have opened before forking. ... get bash(sh) to build a pipe (unnamed) to the child process's fd 3, and either exec that (when it comes)