From patchwork Thu Nov 8 15:55:23 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: socket.7: Correctly describe SO_SNDTIMEO for connect Date: Thu, 08 Nov 2012 05:55:23 -0000 From: Andi Kleen X-Patchwork-Id: 197853 Message-Id: <1352390123-28658-1-git-send-email-andi@firstfloor.org> To: mtk.manpages@gmail.com Cc: linux-man@vger.kernel.org, netdev@vger.kernel.org, Andi Kleen From: Andi Kleen When SO_SNDTIMEO is set before connect() connect may return EWOULDBLOCK when the timeout fires. Describe this correctly. Signed-off-by: Andi Kleen --- man7/socket.7 | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/man7/socket.7 b/man7/socket.7 index cd75746..9e05f48 100644 --- a/man7/socket.7 +++ b/man7/socket.7 @@ -434,6 +434,9 @@ set to .B EAGAIN or .B EWOULDBLOCK +or +.B EINPROGRESS +(for connect) .\" in fact to EAGAIN just as if the socket was specified to be nonblocking. If the timeout is set to zero (the default) @@ -442,6 +445,7 @@ Timeouts only have effect for system calls that perform socket I/O (e.g., .BR read (2), .BR recvmsg (2), .BR send (2), +.BR connect (2), .BR sendmsg (2)); timeouts have no effect for .BR select (2),