Mac OS X has layered bootstrap nameservers. The bottom layer is the
root layer and all others like the console user's layer go on top.
For security, layers can see connections at their level or below, but
not above. This in short means the root layer cannot see any other
connections not in its own layer. But all other layers can see down
into the root layer since they're all above it.
So basically it's not working because the root daemon can't see the
user level's registered connections. You'll have to make one from the
root daemon for the user program to lookup or use a different IPC
flavor.
On Apr 7, 2008, at 4:32 PM, SD wrote:
I have a deamon application that starts up and registers itself
using a pre-defined name. (NSConnection registerName: name]
I have another application that is started and it looks for the
connection with [NSConnection
rootProxyForConnectionWithRegisteredName: name host:nil].
This all works correctly if the processes are all launched with
Xcode or the command line.
If I launch the deamon via command line using my regular user and
then I launch the application using the Security.framework
authentication, the application does not find the connection and
starts a second deamon.
Does anyone know what is going on here and how to fix it so that the
connection is registered for the whole system (not per user as it
appears).
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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]
