On 11.04.2009, at 20:50, Gwynne Raskind wrote:
FWIW, I was having some strange issues with NSTask and setuid child processes (...) My eventual solution was to roll my own version of NSTask which gave me full control over the way the child process was set up, (...) I was able to track down the issue I was having with the setuid process once I had the ability to trace the code running between fork() and execve().
Care to elaborate on what NSTask is doing differently from your solution and what difference this makes (in general and in your particular use case)? Did you just hit an edge case, or is there some fundamental problem that's likely to bite others? Did you file a bug with Apple about this?
Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." http://www.zathras.de _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
