signal.7: Clarify text describing EINTR semantics for socket interfaces

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-05-27 18:32:16 +02:00
parent 9c0381af73
commit 8efc0168ad
1 changed files with 19 additions and 14 deletions

View File

@ -717,29 +717,30 @@ when interrupted by a signal handler:
.\" on interruption by a signal handler.
.RS 4
.IP * 2
Socket interfaces, when a timeout has been set on the socket using
"Input" socket interfaces, when a timeout
.RB ( SO_RCVTIMEO )
has been set on the socket using
.BR setsockopt (2):
.BR accept (2),
.BR recv (2),
.BR recvfrom (2),
.BR recvmmsg (2)
(with a non-NULL
(also with a non-NULL
.IR timeout
argument),
and
.BR recvmsg (2),
if a receive timeout
.BR recvmsg (2).
.IP *
"Output" socket interfaces, when a timeout
.RB ( SO_RCVTIMEO )
has been set;
has been set on the socket using
.BR setsockopt (2):
.BR connect (2),
.BR send (2),
.BR sendto (2),
and
.\" FIXME What about sendmmsg()?
.BR sendmsg (2),
if a send timeout
.RB ( SO_SNDTIMEO )
has been set.
.BR sendmsg (2).
.IP *
Interfaces used to wait for signals:
.BR pause (2),
@ -796,20 +797,24 @@ on other systems.
The Linux interfaces that display this behavior are:
.RS 4
.IP * 2
Socket interfaces, when a timeout has been set on the socket using
"Input" socket interfaces, when a timeout
.RB ( SO_RCVTIMEO )
has been set on the socket using
.BR setsockopt (2):
.BR accept (2),
.BR recv (2),
.BR recvfrom (2),
.BR recvmmsg (2)
(with a non-NULL
(also with a non-NULL
.IR timeout
argument),
and
.BR recvmsg (2),
if a receive timeout
.BR recvmsg (2).
.IP *
"Output" socket interfaces, when a timeout
.RB ( SO_RCVTIMEO )
has been set;
has been set on the socket using
.BR setsockopt (2):
.BR connect (2),
.BR send (2),
.BR sendto (2),