'\" et
.TH RECV "3P" 2013 "IEEE/The Open Group" "POSIX Programmer's Manual"
.SH PROLOG
This manual page is part of the POSIX Programmer's Manual.
The Linux implementation of this interface may differ (consult
the corresponding Linux manual page for details of Linux behavior),
or the interface may not be implemented on Linux.

.SH NAME
recv
\(em receive a message from a connected socket
.SH SYNOPSIS
.LP
.nf
#include <sys/socket.h>
.P
ssize_t recv(int \fIsocket\fP, void *\fIbuffer\fP, size_t \fIlength\fP, int \fIflags\fP);
.fi
.SH DESCRIPTION
The
\fIrecv\fR()
function shall receive a message from a connection-mode or
connectionless-mode socket. It is normally used with connected sockets
because it does not permit the application to retrieve the source
address of received data.
.P
The
\fIrecv\fR()
function takes the following arguments:
.IP "\fIsocket\fR" 10
Specifies the socket file descriptor.
.IP "\fIbuffer\fR" 10
Points to a buffer where the message should be stored.
.IP "\fIlength\fR" 10
Specifies the length in bytes of the buffer pointed to by the
.IR buffer
argument.
.IP "\fIflags\fR" 10
Specifies the type of message reception. Values of this argument are
formed by logically OR'ing zero or more of the following values:
.RS 10 
.IP MSG_PEEK 12
Peeks at an incoming message. The data is treated as unread and the
next
\fIrecv\fR()
or similar function shall still return this data.
.IP MSG_OOB 12
Requests out-of-band data. The significance and semantics of
out-of-band data are protocol-specific.
.IP MSG_WAITALL 12
On SOCK_STREAM sockets this requests that the function block until the
full amount of data can be returned. The function may return the
smaller amount of data if the socket is a message-based socket, if a
signal is caught, if the connection is terminated, if MSG_PEEK was
specified, or if an error is pending for the socket.
.RE
.P
The
\fIrecv\fR()
function shall return the length of the message written to the buffer
pointed to by the
.IR buffer
argument. For message-based sockets, such as SOCK_DGRAM and
SOCK_SEQPACKET, the entire message shall be read in a single operation.
If a message is too long to fit in the supplied buffer, and MSG_PEEK is
not set in the
.IR flags
argument, the excess bytes shall be discarded. For stream-based
sockets, such as SOCK_STREAM, message boundaries shall be ignored. In
this case, data shall be returned to the user as soon as it becomes
available, and no data shall be discarded.
.P
If the MSG_WAITALL flag is not set, data shall be returned only up to
the end of the first message.
.P
If no messages are available at the socket and O_NONBLOCK is not set on
the socket's file descriptor,
\fIrecv\fR()
shall block until a message arrives. If no messages are available at
the socket and O_NONBLOCK is set on the socket's file descriptor,
\fIrecv\fR()
shall fail and set
.IR errno
to
.BR [EAGAIN] 
or
.BR [EWOULDBLOCK] .
.SH "RETURN VALUE"
Upon successful completion,
\fIrecv\fR()
shall return the length of the message in bytes. If no messages are
available to be received and the peer has performed an orderly
shutdown,
\fIrecv\fR()
shall return 0. Otherwise, \(mi1 shall be returned and
.IR errno
set to indicate the error.
.SH ERRORS
The
\fIrecv\fR()
function shall fail if:
.TP
.BR EAGAIN " or " EWOULDBLOCK
.br
The socket's file descriptor is marked O_NONBLOCK and no data is
waiting to be received; or MSG_OOB is set and no out-of-band data is
available and either the socket's file descriptor is marked O_NONBLOCK
or the socket does not support blocking to await out-of-band data.
.TP
.BR EBADF
The
.IR socket
argument is not a valid file descriptor.
.TP
.BR ECONNRESET
A connection was forcibly closed by a peer.
.TP
.BR EINTR
The
\fIrecv\fR()
function was interrupted by a signal that was caught, before any data
was available.
.TP
.BR EINVAL
The MSG_OOB flag is set and no out-of-band data is available.
.TP
.BR ENOTCONN
A receive is attempted on a connection-mode socket that is not
connected.
.TP
.BR ENOTSOCK
The
.IR socket
argument does not refer to a socket.
.TP
.BR EOPNOTSUPP
The specified flags are not supported for this socket type or
protocol.
.TP
.BR ETIMEDOUT
The connection timed out during connection establishment, or due to a
transmission timeout on active connection.
.P
The
\fIrecv\fR()
function may fail if:
.TP
.BR EIO
An I/O error occurred while reading from or writing to the file
system.
.TP
.BR ENOBUFS
Insufficient resources were available in the system to perform the
operation.
.TP
.BR ENOMEM
Insufficient memory was available to fulfill the request.
.LP
.IR "The following sections are informative."
.SH "EXAMPLES"
None.
.SH "APPLICATION USAGE"
The
\fIrecv\fR()
function is equivalent to
\fIrecvfrom\fR()
with null pointer
.IR address
and
.IR address_len
arguments, and to
\fIread\fR()
if the
.IR socket
argument refers to a socket and the
.IR flags
argument is 0.
.P
The
\fIselect\fR()
and
\fIpoll\fR()
functions can be used to determine when data is available to be
received.
.SH "RATIONALE"
None.
.SH "FUTURE DIRECTIONS"
None.
.SH "SEE ALSO"
.IR "\fIpoll\fR\^(\|)",
.IR "\fIpselect\fR\^(\|)",
.IR "\fIread\fR\^(\|)",
.IR "\fIrecvmsg\fR\^(\|)",
.IR "\fIrecvfrom\fR\^(\|)",
.IR "\fIsend\fR\^(\|)",
.IR "\fIsendmsg\fR\^(\|)",
.IR "\fIsendto\fR\^(\|)",
.IR "\fIshutdown\fR\^(\|)",
.IR "\fIsocket\fR\^(\|)",
.IR "\fIwrite\fR\^(\|)"
.P
The Base Definitions volume of POSIX.1\(hy2008,
.IR "\fB<sys_socket.h>\fP"
.SH COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form
from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology
-- Portable Operating System Interface (POSIX), The Open Group Base
Specifications Issue 7, Copyright (C) 2013 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group.
(This is POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
event of any discrepancy between this version and the original IEEE and
The Open Group Standard, the original IEEE and The Open Group Standard
is the referee document. The original Standard can be obtained online at
http://www.unix.org/online.html .

Any typographical or formatting errors that appear
in this page are most likely
to have been introduced during the conversion of the source files to
man page format. To report such errors, see
https://www.kernel.org/doc/man-pages/reporting_bugs.html .