1 .\" $NetBSD: recv.2,v 1.6 1995/02/27 12:36:08 cgd Exp $
3 .\" Copyright (c) 1983, 1990, 1991, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. All advertising materials mentioning features or use of this software
15 .\" must display the following acknowledgement:
16 .\" This product includes software developed by the University of
17 .\" California, Berkeley and its contributors.
18 .\" 4. Neither the name of the University nor the names of its contributors
19 .\" may be used to endorse or promote products derived from this software
20 .\" without specific prior written permission.
22 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .\" @(#)recv.2 8.3 (Berkeley) 2/21/94
43 .Nd receive a message from a socket
45 .Fd #include <sys/types.h>
46 .Fd #include <sys/socket.h>
48 .Fn recv "int s" "void *buf" "size_t len" "int flags"
50 .Fn recvfrom "int s" "void *buf" "size_t len" "int flags" "struct sockaddr *from" "socklen_t *fromlen"
52 .Fn recvmsg "int s" "struct msghdr *msg" "int flags"
57 are used to receive messages from a socket,
58 and may be used to receive data on a socket whether or not
59 it is connection-oriented.
63 is non-nil, and the socket is not connection-oriented,
64 the source address of the message is filled in.
66 is a value-result parameter, initialized to the size of
67 the buffer associated with
69 and modified on return to indicate the actual size of the
74 call is normally used only on a
83 As it is redundant, it may not be supported in future releases.
85 On successful completion, all three routines return the number of
86 message bytes read. If a message is too long to fit in the supplied
87 buffer, excess bytes may be discarded depending on the type of socket
88 the message is received from (see
91 If no messages are available at the socket, the
92 receive call waits for a message to arrive, unless
93 the socket is nonblocking (see
95 in which case the value
96 -1 is returned and the external variable
100 The receive calls normally return any data available,
101 up to the requested amount,
102 rather than waiting for receipt of the full amount requested;
103 this behavior is affected by the socket-level options
112 call may be used to determine when more data arrive.
116 argument to a recv call is formed by
118 one or more of the values:
119 .Bl -column MSG_WAITALL -offset indent
120 .It Dv MSG_OOB Ta process out-of-band data
121 .It Dv MSG_PEEK Ta peek at incoming message
122 .It Dv MSG_WAITALL Ta wait for full request or error
126 flag requests receipt of out-of-band data
127 that would not be received in the normal data stream.
128 Some protocols place expedited data at the head of the normal
129 data queue, and thus this flag cannot be used with such protocols.
130 The MSG_PEEK flag causes the receive operation to return data
131 from the beginning of the receive queue without removing that
133 Thus, a subsequent receive call will return the same data.
134 The MSG_WAITALL flag requests that the operation block until
135 the full request is satisfied.
136 However, the call may still return less data than requested
137 if a signal is caught, an error or disconnect occurs,
138 or the next data to be received is of a different type than that returned.
144 structure to minimize the number of directly supplied parameters.
145 This structure has the following form, as defined in
146 .Ao Pa sys/socket.h Ac :
150 caddr_t msg_name; /* optional address */
151 socklen_t msg_namelen; /* size of address */
152 struct iovec *msg_iov; /* scatter/gather array */
153 u_int msg_iovlen; /* # elements in msg_iov */
154 caddr_t msg_control; /* ancillary data, see below */
155 socklen_t msg_controllen; /* ancillary data buffer len */
156 int msg_flags; /* flags on received message */
164 specify the source address if the socket is unconnected;
166 may be given as a null pointer if no names are desired or required.
170 describe scatter gather locations, as discussed in
175 points to a buffer for other protocol control related messages
176 or other miscellaneous ancillary data.
177 The messages are of the form:
180 u_int cmsg_len; /* data byte count, including hdr */
181 int cmsg_level; /* originating protocol */
182 int cmsg_type; /* protocol-specific type */
184 u_char cmsg_data[]; */
187 As an example, one could use this to learn of changes in the data-stream
188 in XNS/SPP, or in ISO, to obtain user-connection-request data by requesting
189 a recvmsg with no data buffer provided immediately after an
193 Open file descriptors are now passed as ancillary data for
206 field is set on return according to the message received.
208 indicates end-of-record;
209 the data returned completed a record (generally used with sockets of type
210 .Dv SOCK_SEQPACKET ) .
213 the trailing portion of a datagram was discarded because the datagram
214 was larger than the buffer supplied.
217 control data were discarded due to lack of space in the buffer
220 is returned to indicate that expedited or out-of-band data were received.
223 These calls return the number of bytes received, or -1
224 if an error occurred.
231 is an invalid descriptor.
233 The socket is associated with a connection-oriented protocol
234 and has not been connected (see
241 does not refer to a socket.
243 The socket is marked non-blocking, and the receive operation
245 a receive timeout had been set,
246 and the timeout expired before data were received.
248 The receive was interrupted by delivery of a signal before
249 any data were available.
251 The receive buffer pointer(s) point outside the process's
263 function call appeared in