mirror of
https://github.com/zeromq/libzmq.git
synced 2025-02-23 23:16:41 +01:00
Problem: undocumented limit on IPC paths in Linux is 107 chars
Solution: document the limit of 113 chars including ipc://. We might fix this in libzmq by shortening an over-long IPC pathname into a unique string; so long as this is done consistently in bind and in connect, it will save applications from weird failures when they use external data to generate IPC pathnames.
This commit is contained in:
parent
f15146b5d2
commit
51c8c1d67a
@ -53,6 +53,10 @@ namespace shall be used. The abstract namespace is independent of the
|
|||||||
filesystem and if a process attempts to bind an endpoint already bound by a
|
filesystem and if a process attempts to bind an endpoint already bound by a
|
||||||
process, it will fail. See unix(7) for details.
|
process, it will fail. See unix(7) for details.
|
||||||
|
|
||||||
|
NOTE: IPC pathnames have a maximum size that depends on the operating system.
|
||||||
|
On Linux, the maximum is 113 characters including the "ipc://" prefix (107
|
||||||
|
characters for the real path name).
|
||||||
|
|
||||||
Connecting a socket
|
Connecting a socket
|
||||||
~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~
|
||||||
When connecting a 'socket' to a peer address using _zmq_connect()_ with the
|
When connecting a 'socket' to a peer address using _zmq_connect()_ with the
|
||||||
|
Loading…
x
Reference in New Issue
Block a user