Re: Spawn process without inheriting parent stdout, stdin
Re: Spawn process without inheriting parent stdout, stdin
- Subject: Re: Spawn process without inheriting parent stdout, stdin
- From: "Matthew Jaffa" <email@hidden>
- Date: Fri, 30 Sep 2005 16:28:08 -0600
Here is my problem:
App1 calls App2 and App2 calls App3, now App2 depends on the return codes
of App3.
But somehow App2 is always getting the same return code because maybe App1
is swallowing up App3's ouput since he is the overall parent of all of them.
App2 needs to capture App3's stdout but for some reason it seems to be not
returning correctly.
Am I making any sense here???
Thanks,
Matt
From: Sherm Pendley <email@hidden>
To: Matthew Jaffa <email@hidden>
CC: email@hidden
Subject: Re: Spawn process without inheriting parent stdout, stdin
Date: Fri, 30 Sep 2005 18:09:50 -0400
On Sep 30, 2005, at 5:14 PM, Matthew Jaffa wrote:
I was wondering if there is a way to spawn a process programmatically
without the new process inheriting the stdout of the parent. I tried
NSTask, but the newly created processes output from cout and printf will
go to the cocoa app that created it.
Why not simply use NSTask's -setStandardOutput: to redirect the child's
output elsewhere? The argument doesn't have to be an NSPipe - it can be an
NSFileHandle as well.
sherm--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden