[zeromq-dev] IPC address validity

Stephen Lord Steve.Lord at quantum.com
Wed Jan 9 13:50:21 CET 2013

In an ipc address the ipc:// defines the address type,
and the remainder defines the path to the socket. So you are defining
a file system path on your system.


would be test in the current working directory, all processes need to
run in the same directory.


would be /test in the root of the filesystem, you probably need to be
root to create this.


Would be socket in the /test directory. ZMQ will not create the directory
for you so it will fail if it is not present, it will only create the socket 
named pipe itself.

Regular permission checks also apply, so applications need permission
to access the directory component of the socket path.

Read the man page here:



On Jan 9, 2013, at 6:40 AM, Claudio Carbone <erupter at libero.it>

> On 09/01/13 12:52, Ben Gray wrote:
>> On 9 January 2013 11:40, Claudio Carbone <erupter at libero.it> wrote:
>>> On 09/01/13 12:32, Ben Gray wrote:
>>> I'm using 3.2.2 and the only address that works for me is the first.
>>> Would you mind telling me how can I conduct the same test you did?
>>> I don't have any test_delay_connection anywhere, not even in the zeromq
>>> source folder.
>> Turns out it was called test_connect_delay.cpp not
>> test_delay_connection.cpp, sorry about that
> Ben which part did you modify to test the ipc address?
> There are a lot of sockets and I'm unsure which ones are control sockets 
> and which one are transport sockets.
> Regards
> Claudio
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.

More information about the zeromq-dev mailing list