Re: Sandboxing and calling Launchctl
Re: Sandboxing and calling Launchctl
- Subject: Re: Sandboxing and calling Launchctl
- From: Roland King <email@hidden>
- Date: Fri, 01 Jun 2012 17:04:44 +0800
On Jun 1, 2012, at 4:33 PM, Mark Allan wrote:
> Thanks Alex,
>
> Thanks for your reply.
>
> If you're talking about the com.apple.security.inherit entitlement, that only works for helper apps which are launched via fork/exec from the main application. When the helper app is launched by LaunchServices (via SMLoginItemSetEnabled) it crashes immediately as it can't inherit a sandbox from anywhere.
>
> In a last-ditch attempt, I was trying to get around that by:
> Have my helper app launch the main app at startup.
> The main app could then launch a second helper (with com.apple.security.inherit entitlement) to do the scheduling.
> Main app then terminates immediately.
>
> The two problems with that approach are firstly, the sandbox wouldn't let the helper launch my primary app because it's in a different sandbox, and secondly, my understanding of forking is that even if I could do that, when the main app terminates, any process it forked also gets terminated doesn't it?
>
> Mark
Got to admire your determination with this, I just can't believe that nobody knows how to do it but I've googled around and hunted the dev forums and either nobody does know how to do it, hasn't tried it, or they all managed it with zero effort and thus didn't post, I doubt it's the latter.
As to fork(), if your parent dies you live on, just get reparented (to init I think). The question is usually asked the other way around, people wanting child processes to get killed when the parent dies and it can be quite hard.
_______________________________________________
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