]> git.saurik.com Git - apple/xnu.git/blame - bsd/man/man2/recv.2
xnu-792.10.96.tar.gz
[apple/xnu.git] / bsd / man / man2 / recv.2
CommitLineData
9bccf70c
A
1.\" $NetBSD: recv.2,v 1.6 1995/02/27 12:36:08 cgd Exp $
2.\"
3.\" Copyright (c) 1983, 1990, 1991, 1993
4.\" The Regents of the University of California. All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
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.
21.\"
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
32.\" SUCH DAMAGE.
33.\"
34.\" @(#)recv.2 8.3 (Berkeley) 2/21/94
35.\"
36.Dd February 21, 1994
37.Dt RECV 2
38.Os BSD 4.3r
39.Sh NAME
40.Nm recv ,
41.Nm recvfrom ,
42.Nm recvmsg
43.Nd receive a message from a socket
44.Sh SYNOPSIS
45.Fd #include <sys/types.h>
46.Fd #include <sys/socket.h>
47.Ft ssize_t
48.Fn recv "int s" "void *buf" "size_t len" "int flags"
49.Ft ssize_t
91447636 50.Fn recvfrom "int s" "void *buf" "size_t len" "int flags" "struct sockaddr *from" "socklen_t *fromlen"
9bccf70c
A
51.Ft ssize_t
52.Fn recvmsg "int s" "struct msghdr *msg" "int flags"
53.Sh DESCRIPTION
54.Fn Recvfrom
55and
56.Fn recvmsg
57are used to receive messages from a socket,
58and may be used to receive data on a socket whether or not
59it is connection-oriented.
60.Pp
61If
62.Fa from
63is non-nil, and the socket is not connection-oriented,
64the source address of the message is filled in.
65.Fa Fromlen
66is a value-result parameter, initialized to the size of
67the buffer associated with
68.Fa from ,
69and modified on return to indicate the actual size of the
70address stored there.
71.Pp
72The
73.Fn recv
74call is normally used only on a
75.Em connected
76socket (see
77.Xr connect 2 )
78and is identical to
79.Fn recvfrom
80with a nil
81.Fa from
82parameter.
83As it is redundant, it may not be supported in future releases.
84.Pp
85On successful completion, all three routines return the number of
86message bytes read. If a message is too long to fit in the supplied
87buffer, excess bytes may be discarded depending on the type of socket
88the message is received from (see
89.Xr socket 2 ) .
90.Pp
91If no messages are available at the socket, the
92receive call waits for a message to arrive, unless
93the socket is nonblocking (see
94.Xr fcntl 2 )
95in which case the value
96-1 is returned and the external variable
97.Va errno
98set to
99.Er EAGAIN .
100The receive calls normally return any data available,
101up to the requested amount,
102rather than waiting for receipt of the full amount requested;
103this behavior is affected by the socket-level options
104.Dv SO_RCVLOWAT
105and
106.Dv SO_RCVTIMEO
107described in
108.Xr getsockopt 2 .
109.Pp
110The
111.Xr select 2
112call may be used to determine when more data arrive.
113.Pp
114The
115.Fa flags
116argument to a recv call is formed by
117.Em or Ap ing
118one 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
123.El
124The
125.Dv MSG_OOB
126flag requests receipt of out-of-band data
127that would not be received in the normal data stream.
128Some protocols place expedited data at the head of the normal
129data queue, and thus this flag cannot be used with such protocols.
130The MSG_PEEK flag causes the receive operation to return data
131from the beginning of the receive queue without removing that
132data from the queue.
133Thus, a subsequent receive call will return the same data.
134The MSG_WAITALL flag requests that the operation block until
135the full request is satisfied.
136However, the call may still return less data than requested
137if a signal is caught, an error or disconnect occurs,
138or the next data to be received is of a different type than that returned.
139.Pp
140The
141.Fn recvmsg
142call uses a
143.Fa msghdr
144structure to minimize the number of directly supplied parameters.
145This structure has the following form, as defined in
146.Ao Pa sys/socket.h Ac :
147.Pp
148.Bd -literal
149struct msghdr {
91447636
A
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 */
9bccf70c
A
157};
158.Ed
159.Pp
160Here
161.Fa msg_name
162and
163.Fa msg_namelen
164specify the source address if the socket is unconnected;
165.Fa msg_name
166may be given as a null pointer if no names are desired or required.
167.Fa Msg_iov
168and
169.Fa msg_iovlen
170describe scatter gather locations, as discussed in
171.Xr read 2 .
172.Fa Msg_control ,
173which has length
174.Fa msg_controllen ,
175points to a buffer for other protocol control related messages
176or other miscellaneous ancillary data.
177The messages are of the form:
178.Bd -literal
179struct cmsghdr {
180 u_int cmsg_len; /* data byte count, including hdr */
181 int cmsg_level; /* originating protocol */
182 int cmsg_type; /* protocol-specific type */
183/* followed by
184 u_char cmsg_data[]; */
185};
186.Ed
187As an example, one could use this to learn of changes in the data-stream
188in XNS/SPP, or in ISO, to obtain user-connection-request data by requesting
189a recvmsg with no data buffer provided immediately after an
190.Fn accept
191call.
192.Pp
193Open file descriptors are now passed as ancillary data for
194.Dv AF_UNIX
195domain sockets, with
196.Fa cmsg_level
197set to
198.Dv SOL_SOCKET
199and
200.Fa cmsg_type
201set to
202.Dv SCM_RIGHTS .
203.Pp
204The
205.Fa msg_flags
206field is set on return according to the message received.
207.Dv MSG_EOR
208indicates end-of-record;
209the data returned completed a record (generally used with sockets of type
210.Dv SOCK_SEQPACKET ) .
211.Dv MSG_TRUNC
212indicates that
213the trailing portion of a datagram was discarded because the datagram
214was larger than the buffer supplied.
215.Dv MSG_CTRUNC
216indicates that some
217control data were discarded due to lack of space in the buffer
218for ancillary data.
219.Dv MSG_OOB
220is returned to indicate that expedited or out-of-band data were received.
221.Pp
222.Sh RETURN VALUES
223These calls return the number of bytes received, or -1
224if an error occurred.
225.Sh ERRORS
226The calls fail if:
227.Bl -tag -width Er
228.It Bq Er EBADF
229The argument
230.Fa s
231is an invalid descriptor.
232.It Bq Er ENOTCONN
233The socket is associated with a connection-oriented protocol
234and has not been connected (see
235.Xr connect 2
236and
237.Xr accept 2 ).
238.It Bq Er ENOTSOCK
239The argument
240.Fa s
241does not refer to a socket.
242.It Bq Er EAGAIN
243The socket is marked non-blocking, and the receive operation
244would block, or
245a receive timeout had been set,
246and the timeout expired before data were received.
247.It Bq Er EINTR
248The receive was interrupted by delivery of a signal before
249any data were available.
250.It Bq Er EFAULT
251The receive buffer pointer(s) point outside the process's
252address space.
253.El
254.Sh SEE ALSO
255.Xr fcntl 2 ,
256.Xr read 2 ,
257.Xr select 2 ,
258.Xr getsockopt 2 ,
259.Xr socket 2
260.Sh HISTORY
261The
262.Fn recv
263function call appeared in
264.Bx 4.2 .