nn_ipc man page on DragonFly

nn_ipc man page on DragonFly

Man page or keyword search:
man Server 44335 pages
apropos Keyword Search (all sections)
Output format

NN_IPC(7)			nanomsg manual			     NN_IPC(7)

NAME
       nn_ipc - inter-process transport mechanism

SYNOPSIS
       #include <nanomsg/nn.h>

       #include <nanomsg/ipc.h>

DESCRIPTION
       Inter-process transport allows for sending messages between processes
       within a single box. The implementation uses native IPC mechanism
       provided by the local operating system and the IPC addresses are thus
       OS-specific.

       On POSIX-compliant systems, UNIX domain sockets are used and IPC
       addresses are file references. Note that both relative (ipc://test.ipc)
       and absolute (ipc:///tmp/test.ipc) paths may be used. Also note that
       access rights on the IPC files must be set in such a way that the
       appropriate applications can actually use them.

       On Windows, named pipes are used for IPC. IPC address is an arbitrary
       case-insensitive string containing any character except for backslash.
       Internally, address ipc://test means that named pipe \\.\pipe\test will
       be used.

EXAMPLE
	   nn_bind (s1, "ipc:///tmp/test.ipc");
	   nn_connect (s2, "ipc:///tmp/test.ipc");

SEE ALSO
       nn_inproc(7) nn_tcp(7) nn_bind(3) nn_connect(3) nanomsg(7)

AUTHORS
       Martin Sustrik <sustrik@250bpm.com[1]>

NOTES
	1. sustrik@250bpm.com
	   mailto:sustrik@250bpm.com

nanomsg Unknown			  12/23/2015			     NN_IPC(7)

[top]

List of man pages available for DragonFly

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]

Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................

Vote for polarhome