See https://gist.github.com/3751746 for details.
Basically, in Node 0.6, if you start a child_process with
child_process.spawn, the pipe2 system call was used to create the
pipes between parent and child.
This was changed (I believe) in this commit by indutny:
https://github.com/joyent/libuv/comm
On Wed, Sep 19, 2012 at 9:54 PM, David Glasser wrote:
> See https://gist.github.com/3751746 for details.
>
> Basically, in Node 0.6, if you start a child_process with
> child_process.spawn, the pipe2 system call was used to create the
> pipes between parent and child.
>
> This was changed (I belie
Ah, yes, that'll do it. And yes, that's the workaround we're using.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to
Hello,
So, I'm still trying to understand the implications of this change. Suppose
I spawn "cat" and write to the stdin of the spawned process, then will the
"cat" process not be able to read it?
var cat = spawn('cat');
cat.stdin.write('Foo Bar');
cat.stdout.on('data', function(d) { console.log
On Thu, Sep 20, 2012 at 4:07 PM, dhruvbird wrote:
> Hello,
>
> So, I'm still trying to understand the implications of this change. Suppose
> I spawn "cat" and write to the stdin of the spawned process, then will the
> "cat" process not be able to read it?
>
> var cat = spawn('cat');
> cat.stdin.wr
Ben,
I noticed this line in the announcement for 0.8.10
* unix: put child process stdio fds in blocking mode (Ben Noordhuis)
Does that by any chance address this issue? I continue to struggle with it.
Thanks,
Shawn
On Thu, Sep 20, 2012 at 9:18 AM, Ben Noordhuis wrote:
> On Thu, Sep 20, 2012
On Wed, Sep 26, 2012 at 12:43 AM, Shawn Parrish wrote:
> Ben,
>
> I noticed this line in the announcement for 0.8.10
>
> * unix: put child process stdio fds in blocking mode (Ben Noordhuis)
>
> Does that by any chance address this issue? I continue to struggle with it.
No, that fixes another iss
