Adding upstream version 4.23.0.upstream/4.23.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 21 insertions, 21 deletions

diff --git a/upstream/opensuse-tumbleweed/man2/socket.2 b/upstream/opensuse-tumbleweed/man2/socket.2
index 2a35f2b7..cf41c2f0 100644
--- a/upstream/opensuse-tumbleweed/man2/socket.2
+++ b/upstream/opensuse-tumbleweed/man2/socket.2
@@ -12,7 +12,7 @@
 .\" Modified 2002-07-17 by Michael Kerrisk <mtk.manpages@gmail.com>
 .\" Modified 2004-06-17 by Michael Kerrisk <mtk.manpages@gmail.com>
 .\"
-.TH socket 2 2023-03-30 "Linux man-pages 6.05.01"
+.TH socket 2 2024-05-02 "Linux man-pages (unreleased)"
 .SH NAME
 socket \- create an endpoint for communication
 .SH LIBRARY
@@ -21,7 +21,7 @@ Standard C library
 .SH SYNOPSIS
 .nf
 .B #include <sys/socket.h>
-.PP
+.P
 .BI "int socket(int " domain ", int " type ", int " protocol );
 .fi
 .SH DESCRIPTION
@@ -30,7 +30,7 @@ creates an endpoint for communication and returns a file descriptor
 that refers to that endpoint.
 The file descriptor returned by a successful call will be
 the lowest-numbered file descriptor not currently open for the process.
-.PP
+.P
 The
 .I domain
 argument specifies a communication domain; this selects the protocol
@@ -79,7 +79,7 @@ T}:AppleTalk:T{
 T}
 T{
 .B AF_X25
-T}:ITU-T X.25 / ISO-8208 protocol:T{
+T}:ITU-T X.25 / ISO/IEC\~8208 protocol:T{
 .BR x25 (7)
 T}
 T{
@@ -193,11 +193,11 @@ T}:T{
 XDP (express data path) interface
 T}
 .TE
-.PP
+.P
 Further details of the above address families,
 as well as information on several other address families, can be found in
 .BR address_families (7).
-.PP
+.P
 The socket has the indicated
 .IR type ,
 which specifies the communication semantics.
@@ -227,9 +227,9 @@ Provides a reliable datagram layer that does not guarantee ordering.
 Obsolete and should not be used in new programs;
 see
 .BR packet (7).
-.PP
+.P
 Some socket types may not be implemented by all protocol families.
-.PP
+.P
 Since Linux 2.6.27, the
 .I type
 argument serves a second purpose:
@@ -257,7 +257,7 @@ See the description of the
 flag in
 .BR open (2)
 for reasons why this may be useful.
-.PP
+.P
 The
 .I protocol
 specifies a particular protocol to be used with the socket.
@@ -273,7 +273,7 @@ in which communication is to take place; see
 See
 .BR getprotoent (3)
 on how to map protocol name strings to protocol numbers.
-.PP
+.P
 Sockets of type
 .B SOCK_STREAM
 are full-duplex byte streams.
@@ -303,7 +303,7 @@ Out-of-band data may also be transmitted as described in
 .BR send (2)
 and received as described in
 .BR recv (2).
-.PP
+.P
 The communications protocols which implement a
 .B SOCK_STREAM
 ensure that data is not lost or duplicated.
@@ -329,7 +329,7 @@ The only difference is that
 calls will return only the amount of data requested,
 and any data remaining in the arriving packet will be discarded.
 Also all message boundaries in incoming datagrams are preserved.
-.PP
+.P
 .B SOCK_DGRAM
 and
 .B SOCK_RAW
@@ -339,14 +339,14 @@ calls.
 Datagrams are generally received with
 .BR recvfrom (2),
 which returns the next datagram along with the address of its sender.
-.PP
+.P
 .B SOCK_PACKET
 is an obsolete socket type to receive raw packets directly from the
 device driver.
 Use
 .BR packet (7)
 instead.
-.PP
+.P
 An
 .BR fcntl (2)
 .B F_SETOWN
@@ -369,7 +369,7 @@ call with the
 or
 .B SIOCSPGRP
 argument.
-.PP
+.P
 When the network signals an error condition to the protocol module (e.g.,
 using an ICMP message for IP) the pending error flag is set for the socket.
 The next operation on this socket will return the error code of the pending
@@ -379,7 +379,7 @@ to retrieve detailed information about the error; see
 .B IP_RECVERR
 in
 .BR ip (7).
-.PP
+.P
 The operation of sockets is controlled by socket level
 .IR options .
 These options are defined in
@@ -425,24 +425,24 @@ created until sufficient resources are freed.
 .B EPROTONOSUPPORT
 The protocol type or the specified protocol is not
 supported within this domain.
-.PP
+.P
 Other errors may be generated by the underlying protocol modules.
 .SH STANDARDS
 POSIX.1-2008.
-.PP
+.P
 .B SOCK_NONBLOCK
 and
 .B SOCK_CLOEXEC
 are Linux-specific.
 .SH HISTORY
 POSIX.1-2001, 4.4BSD.
-.PP
+.P
 .BR socket ()
 appeared in 4.2BSD.
 It is generally portable to/from
 non-BSD systems supporting clones of the BSD socket layer (including
 System\ V variants).
-.PP
+.P
 The manifest constants used under 4.x BSD for protocol families
 are
 .BR PF_UNIX ,
@@ -485,7 +485,7 @@ is shown in
 .BR tcp (7),
 .BR udp (7),
 .BR unix (7)
-.PP
+.P
 \[lq]An Introductory 4.3BSD Interprocess Communication Tutorial\[rq]
 and
 \[lq]BSD Interprocess Communication Tutorial\[rq],