[zeromq-dev] IPC REQ/REP socket unavailable to other users?
ph at imatix.com
Wed Aug 11 13:42:43 CEST 2010
This seems to be a standard problem with Unix domain sockets shared
between processes that run under different user ids.
You might try creating a subdirectory with the right permissions, and
creating the sockets within that.
If that does not help, please post an issue to the Git issue tracker,
with simple sample code to reproduce the problem. 0MQ would need to
modify the socket permissions after creating the socket and before
On Tue, Aug 10, 2010 at 9:00 PM, Dana Leonard <dleonar at gmail.com> wrote:
> Hi everyone,
> I've found a strange socket behavior on a Red Hat linux box today. I
> have a server process that opens an IPC REQ/REP socket that is used to
> accept association requests from clients. Clients can use this socket just
> fine, as long as the client process is executed by the same user who
> executed the server. For example: User A starts the server. User A starts a
> client process and it associates with the server fine. User B starts another
> client, and it fails while connecting to the socket.
> Is this a standard behavior for IPC sockets on Unix or does the socket
> need additional configuration to allow different users to use it? I have
> tried changing the permissions on the socket to 777 to no avail. Even root
> cannot use a socket created by another user. Has anyone run into this before
> and figured out how to fix it?
> By the way, the "run everything as the same user" solution does not fit
> the requirements of our project.
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
More information about the zeromq-dev