I've got a launchd daemon that uses a domain socket for communicating
On some (most) systems it installs and runs fine. The socket
permissions are 140777 octal, so that anyone on the system can access
the services the daemon is offering.
On some customer systems the same install package ends up creating a
domain socket with permissions 140755 octal, which means that normal
users can't talk to that socket.
It's the same install packet in both cases, and the permissions and
locations of the .plist file and daemon binary are the same, and the
directory permissions for the domain socket directory and it's parent
are the same in all cases.
Does anyone have a clue about why this might be happening?
Any suggestions would be appreciated.
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden