Print this page
3769 Implement SOCK_NONBLOCK flag to socket()
Reviewed-by: Robert Mustacchi <rm@joyent.com>

*** 98,107 **** --- 98,129 ---- file descriptor to be closed prior to any future calls to \fBexec\fR(2). This is similar in purpose to the \fBO_CLOEXEC\fR flag to \fBopen\fR(2). .RE .sp + .ne 2 + .na + \fB\fBSOCK_NDELAY\fR\fR + .ad + .RS 12n + Creates the socket with the \fBO_NDELAY\fR flag set, causing the socket to + provide nonblocking semantics as described for \fBO_NDELAY\fR in \fBopen\fR(2). + \fBSOCK_NONBLOCK\fR should normally be used in preference to \fBSOCK_NDELAY\fR, + and takes precedence if both are set. See \fBopen\fR(2) for further details. + .RE + + .sp + .ne 2 + .na + \fB\fBSOCK_NONBLOCK\fR\fR + .ad + .RS 12n + Creates the socket with the \fBO_NONBLOCK\fR flag set, causing the socket to + provide nonblocking semantics as described for \fBO_NONBLOCK\fR in \fBopen\fR(2). + .RE + + .sp .LP There must be an entry in the \fBnetconfig\fR(4) file for at least each protocol family and type required. If a non-zero protocol has been specified but no exact match for the protocol family, type, and protocol is found, then the first entry containing the specified family and type with a \fIprotocol\fR
*** 262,271 **** --- 284,302 ---- .ad .RS 19n The socket type is not supported by the protocol. .RE + .sp + .ne 2 + .na + \fB\fBEINVAL\fR\fR + .ad + .RS 19n + One or more of the specified flags is not supported. + .RE + .SH ATTRIBUTES .sp .LP See \fBattributes\fR(5) for descriptions of the following attributes: .sp