Re: Launchd domain socket permission problem
Re: Launchd domain socket permission problem
- Subject: Re: Launchd domain socket permission problem
- From: Peter Bierman <email@hidden>
- Date: Fri, 4 Aug 2006 13:58:09 -0700
At 11:01 AM -0700 8/4/06, Kevin Brock wrote:
I've got a launchd daemon that uses a domain socket for
communicating with applications.
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?
If this is an Apple Installer package (.pkg or .mpkg) then the
question might be better asked on the email@hidden
mailing list.
My first guess would be the umask. For that to be involved, you might
be creating the socket from a script instead of as part of your
package payload. Either have your application create the socket at
runtime and assign correct permissions then, or make the socket part
of your package payload.
-pmb
_______________________________________________
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