summaryrefslogtreecommitdiffstats
path: root/man2/getpeername.2
diff options
context:
space:
mode:
Diffstat (limited to 'man2/getpeername.2')
-rw-r--r--man2/getpeername.226
1 files changed, 13 insertions, 13 deletions
diff --git a/man2/getpeername.2 b/man2/getpeername.2
index dc216c0f6..c7243f93c 100644
--- a/man2/getpeername.2
+++ b/man2/getpeername.2
@@ -82,35 +82,35 @@ POSIX.1-2001, SVr4, 4.4BSD
(first appeared in 4.2BSD).
.SH NOTES
For stream sockets, once a
-.BR connect (2)
+.MR connect 2
has been performed, either socket can call
.BR getpeername ()
to obtain the address of the peer socket.
On the other hand, datagram sockets are connectionless.
Calling
-.BR connect (2)
+.MR connect 2
on a datagram socket merely sets the peer address for outgoing
datagrams sent with
-.BR write (2)
+.MR write 2
or
-.BR recv (2).
+.MR recv 2 .
The caller of
-.BR connect (2)
+.MR connect 2
can use
.BR getpeername ()
to obtain the peer address that it earlier set for the socket.
However, the peer socket is unaware of this information, and calling
.BR getpeername ()
on the peer socket will return no useful information (unless a
-.BR connect (2)
+.MR connect 2
call was also executed on the peer).
Note also that the receiver of a datagram can obtain
the address of the sender when using
-.BR recvfrom (2).
+.MR recvfrom 2 .
.SH SEE ALSO
-.BR accept (2),
-.BR bind (2),
-.BR getsockname (2),
-.BR ip (7),
-.BR socket (7),
-.BR unix (7)
+.MR accept 2 ,
+.MR bind 2 ,
+.MR getsockname 2 ,
+.MR ip 7 ,
+.MR socket 7 ,
+.MR unix 7