From b60342ae1a95dbb303705f5b89a94b33805a3841 Mon Sep 17 00:00:00 2001 From: Martin Sustrik Date: Thu, 14 Jan 2010 14:11:34 +0100 Subject: man pages are more specific on NIC name issue --- man/man3/zmq_connect.3 | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'man/man3/zmq_connect.3') diff --git a/man/man3/zmq_connect.3 b/man/man3/zmq_connect.3 index 291d113..dd0b5d8 100644 --- a/man/man3/zmq_connect.3 +++ b/man/man3/zmq_connect.3 @@ -5,17 +5,21 @@ zmq_connect \- connect the socket to the specified peer .B int zmq_connect (void *s, const char *addr); .SH DESCRIPTION The function connect socket -.IR s to the peer identified by +.IR s +to the peer identified by .IR addr . Actual semantics of the command depend on the underlying transport mechanism, however, in cases where peers connect in an asymetric manner, .IR zmq_bind should be called first, .IR zmq_connect -afterwards. For actual formats of +afterwards. Formats of the .IR addr -parameter for different types of transport have a look at -.IR zmq(7) . +parameter are defined by individual transports. For a list of supported +transports have a look at +.IR zmq(7) +manual page. + Note that single socket can be connected (and bound) to arbitrary number of peers using different transport mechanisms. .SH RETURN VALUE -- cgit v1.2.3