Re: CFMessagePortCreateRemote, launchd, Bootstrap Namespace, 10.5
Re: CFMessagePortCreateRemote, launchd, Bootstrap Namespace, 10.5
- Subject: Re: CFMessagePortCreateRemote, launchd, Bootstrap Namespace, 10.5
- From: Jerry Krinock <email@hidden>
- Date: Sat, 10 Sep 2011 20:52:33 -0700
On 2011 Sep 05, at 03:53, Quinn The Eskimo! wrote:
> Mac OS 10.6 and later are less restrictive when it comes to bootstrap namespaces than Mac OS X 10.5.x.
Ah, that's why I had trouble believing my eyes. First time I've ever seen restrictions loosened up!
> My guess is that that the problem you're seeing is that your agent is being launched into the wrong namespace. If you were submitting the job via "launchctl load", you could use "-S" to configure which session type, and hence which namespace, the job went into. With "launchctl submit", I have no idea where you end up.
Can't. The 'submit' subcommand does not offer that option.
> To test this out, create a launchd property list file for your agent, set LimitLoadToSessionTypes to "Aqua", and then launch it via "launchctl load -S Aqua …".
Yes, that works and so your explanation is correct. But the LimitLoadToSessionTypes=Aqua in the plist file is not needed.
> btw There's a launchd-dev mailing list that's more appropriate for launchd questions.
Indeed. At first I thought this was an issue with CFMessagePort.
Thank you, Quinn. _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
- Prev by Date:
Re: CFMessagePortCreateRemote, launchd, Bootstrap Namespace, 10.5
- Next by Date:
Re: CFMessagePortCreateRemote, launchd, Bootstrap Namespace, 10.5
- Previous by thread:
Re: CFMessagePortCreateRemote, launchd, Bootstrap Namespace, 10.5
- Next by thread:
Re: CFMessagePortCreateRemote, launchd, Bootstrap Namespace, 10.5
- Index(es):