Setting the "it is a socket" bits in the path mode is... um...
probably a very bad idea. But it may not explain what you're seeing.
Can you change it to 511 (octal 777) and see if that makes a
difference?
We tried various permissions in the plist, and they didn't make a
difference. It's like launchd on those systems is using some other
source for its permissions. All of the systems in question were
running 10.4.5.
For the time being I'm going to have to hack around this by having
the daemon explicitly set the socket permissions for that socket at
runtime if possible...
Kevin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
