The socket is not created by the installer. The socket is created
by launchd when launchd runs, using a launchd schema, and if I
stop and restart launchd I can see it set the permissions back to
755 each time on the affected systems, even though the permissions
in the launchd .plist say that the socket should be 777.
If it's a umask problem it would have to be a umask for launchd in
general, and I'd expect that to break all *kinds* of things.
That is odd. Can you show me your plist?
This plist works fine on most systems... I've verified that the
plist file on the broken system (there are multiple systems, but I've
only personally examined one) matches this one.
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
This email sent to email@hidden
