Re: Any caveats to using fork in a Foundation/CoreFoundation tool?
Re: Any caveats to using fork in a Foundation/CoreFoundation tool?
- Subject: Re: Any caveats to using fork in a Foundation/CoreFoundation tool?
- From: Jim Correia <email@hidden>
- Date: Thu, 25 Oct 2007 13:48:21 -0400
On Oct 25, 2007, at 1:12 PM, Chris Parker wrote:
Any other recommended approaches?
Using launchd or LaunchServices is really the way to go here; go
ahead and use CFMessagePort for your IPC, but either use a launchd
plist to start your non-GUI process on-demand, or have your GUI
process use LaunchServices to fire it up.
I don't think launchd is the solution I want, since I really want to
directly spawn the process, but then have it detach from the parent.
(I seem to recall there being issues with per user agents on 10.4 as
well.)
Can I use LaunchServices to fire up the process if it is a non-GUI
CoreServices type tool?
When I tried that, LS returned -10822 - kLSServerCommunicationErr.
Am I missing something?
Thanks,
Jim
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden