[Bug 14723] Undocumented behaviour of connect() with SO_SNDTIMEO

[bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org]

https://bugzilla.kernel.org/show_bug.cgi?id=14723

Jorge Nerín <jnerin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jnerin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

--- Comment #1 from Jorge Nerín <jnerin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
From man-pages-3.51 socket(7):

       SO_RCVTIMEO and SO_SNDTIMEO
              Specify the receiving or sending timeouts until reporting an
error.  The
              argument is a struct timeval.  If an input or output function
blocks for
              this  period  of  time,  and  data has been sent or received, the
return
              value of that function will be the amount of  data  transferred; 
if  no
              data  has  been  transferred and the timeout has been reached
then -1 is
              returned with errno set to EAGAIN or EWOULDBLOCK,  or 
EINPROGRESS  (for
              connect(2))  just  as if the socket was specified to be
nonblocking.  If
              the timeout is set to zero (the default) then the operation  will
 never
              timeout.  Timeouts only have effect for system calls that perform
socket
              I/O (e.g., read(2), recvmsg(2), send(2), sendmsg(2)); timeouts 
have  no
              effect for select(2), poll(2), epoll_wait(2), and so on.


I think this bug can be closed.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html