From 0db324e2e5d9d3347ea0e93138372fb65aac09e6 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Mon, 15 Apr 2024 21:41:09 +0200
Subject: Merging upstream version 6.7.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 man2/send.2 | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)

(limited to 'man2/send.2')

diff --git a/man2/send.2 b/man2/send.2
index 16c58b5..79abcc7 100644
--- a/man2/send.2
+++ b/man2/send.2
@@ -9,7 +9,7 @@
 .\" Modified Oct 2003 by aeb
 .\" Modified 2004-07-01 by mtk
 .\"
-.TH send 2 2023-03-30 "Linux man-pages 6.05.01"
+.TH send 2 2024-02-18 "Linux man-pages 6.7"
 .SH NAME
 send, sendto, sendmsg \- send a message on a socket
 .SH LIBRARY
@@ -18,7 +18,7 @@ Standard C library
 .SH SYNOPSIS
 .nf
 .B #include <sys/socket.h>
-.PP
+.P
 .BI "ssize_t send(int " sockfd ", const void " buf [. len "], size_t " len \
 ", int " flags );
 .BI "ssize_t sendto(int " sockfd ", const void " buf [. len "], size_t " len \
@@ -34,7 +34,7 @@ The system calls
 and
 .BR sendmsg ()
 are used to transmit a message to another socket.
-.PP
+.P
 The
 .BR send ()
 call may be used only when the socket is in a
@@ -53,25 +53,25 @@ argument,
 is equivalent to
 .BR write (2).
 Also, the following call
-.PP
+.P
 .in +4n
 .EX
 send(sockfd, buf, len, flags);
 .EE
 .in
-.PP
+.P
 is equivalent to
-.PP
+.P
 .in +4n
 .EX
 sendto(sockfd, buf, len, flags, NULL, 0);
 .EE
 .in
-.PP
+.P
 The argument
 .I sockfd
 is the file descriptor of the sending socket.
-.PP
+.P
 If
 .BR sendto ()
 is used on a connection-mode
@@ -99,7 +99,7 @@ the address of the target is given by
 with
 .I msg.msg_namelen
 specifying its size.
-.PP
+.P
 For
 .BR send ()
 and
@@ -115,16 +115,16 @@ the message is pointed to by the elements of the array
 The
 .BR sendmsg ()
 call also allows sending ancillary data (also known as control information).
-.PP
+.P
 If the message is too long to pass atomically through the
 underlying protocol, the error
 .B EMSGSIZE
 is returned, and the message is not transmitted.
-.PP
+.P
 No indication of failure to deliver is implicit in a
 .BR send ().
 Locally detected errors are indicated by a return value of \-1.
-.PP
+.P
 When the message does not fit into the send buffer of the socket,
 .BR send ()
 normally blocks, unless the socket has been placed in nonblocking I/O
@@ -184,7 +184,7 @@ is a per-call option, whereas
 is a setting on the open file description (see
 .BR open (2)),
 which will affect all threads in the calling process
-and as well as other processes that hold file descriptors
+as well as other processes that hold file descriptors
 referring to the same open file description.
 .TP
 .BR MSG_EOR " (since Linux 2.2)"
@@ -273,7 +273,7 @@ The definition of the
 structure employed by
 .BR sendmsg ()
 is as follows:
-.PP
+.P
 .in +4n
 .EX
 struct msghdr {
@@ -287,7 +287,7 @@ struct msghdr {
 };
 .EE
 .in
-.PP
+.P
 The
 .I msg_name
 field is used on an unconnected socket to specify the target
@@ -297,14 +297,14 @@ It points to a buffer containing the address; the
 field should be set to the size of the address.
 For a connected socket, these fields should be specified as NULL and 0,
 respectively.
-.PP
+.P
 The
 .I msg_iov
 and
 .I msg_iovlen
 fields specify scatter-gather locations, as for
 .BR writev (2).
-.PP
+.P
 You may send control information (ancillary data) using the
 .I msg_control
 and
@@ -320,7 +320,7 @@ socket domains, see
 .BR unix (7)
 and
 .BR ip (7).
-.PP
+.P
 The
 .I msg_flags
 field is ignored.
@@ -458,13 +458,13 @@ but glibc currently types both as
 .\" as (at least with GCC) is int.
 .SH STANDARDS
 POSIX.1-2008.
-.PP
+.P
 .B MSG_CONFIRM
 is a Linux extension.
 .SH HISTORY
 4.4BSD, SVr4, POSIX.1-2001.
 (first appeared in 4.2BSD).
-.PP
+.P
 POSIX.1-2001 describes only the
 .B MSG_OOB
 and
-- 
cgit v1.2.3