From bbc5befc66f187a769982b57b64712dbcc317250 Mon Sep 17 00:00:00 2001 From: Pieter Hintjens Date: Mon, 14 Jan 2013 17:49:19 +0100 Subject: [PATCH] Clarified zmq_bind on icp:// --- doc/zmq_ipc.txt | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/doc/zmq_ipc.txt b/doc/zmq_ipc.txt index 4d9f6f1f..4d34ac53 100644 --- a/doc/zmq_ipc.txt +++ b/doc/zmq_ipc.txt @@ -39,9 +39,14 @@ When the address is `*`, _zmq_bind()_ shall generate a unique temporary pathname. The caller should retrieve this pathname using the ZMQ_LAST_ENDPOINT socket option. See linkzmq:zmq_getsockopt[3] for details. -NOTE: any existing binding to the same endpoint shall be overridden. In this -behavior, the 'ipc' transport is not consistent with the 'tcp' or 'inproc' -transports. +NOTE: any existing binding to the same endpoint shall be overridden. That is, +if a second process binds to an endpoint already bound by a process, this +will succeed and the first process will lose its binding. In this behavior, +the 'ipc' transport is not consistent with the 'tcp' or 'inproc' transports. + +NOTE: the endpoint pathname must be writable by the process. When the endpoint +starts with '/', e.g., `ipc:///pathname`, this will be an _absolute_ pathname. +If the endpoint specifies a directory that does not exist, the bind shall fail. Connecting a socket ~~~~~~~~~~~~~~~~~~~ @@ -83,3 +88,7 @@ AUTHORS ------- This 0MQ manual page was written by Pieter Hintjens , Martin Sustrik and Martin Lucina . + + + +