xref: /freebsd-12.1/lib/libc/sys/send.2 (revision bb487d2b)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 4. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\"     From: @(#)send.2	8.2 (Berkeley) 2/21/94
29.\" $FreeBSD$
30.\"
31.Dd January 29, 2016
32.Dt SEND 2
33.Os
34.Sh NAME
35.Nm send ,
36.Nm sendto ,
37.Nm sendmsg ,
38.Nm sendmmsg
39.Nd send message(s) from a socket
40.Sh LIBRARY
41.Lb libc
42.Sh SYNOPSIS
43.In sys/types.h
44.In sys/socket.h
45.Ft ssize_t
46.Fn send "int s" "const void *msg" "size_t len" "int flags"
47.Ft ssize_t
48.Fn sendto "int s" "const void *msg" "size_t len" "int flags" "const struct sockaddr *to" "socklen_t tolen"
49.Ft ssize_t
50.Fn sendmsg "int s" "const struct msghdr *msg" "int flags"
51.Ft ssize_t
52.Fn sendmmsg "int s" "struct mmsghdr * restrict msgvec" "size_t vlen" "int flags"
53.Sh DESCRIPTION
54The
55.Fn send
56and
57.Fn sendmmsg
58functions,
59and
60.Fn sendto
61and
62.Fn sendmsg
63system calls
64are used to transmit one or more messages (with the
65.Fn sendmmsg
66call) to
67another socket.
68The
69.Fn send
70function
71may be used only when the socket is in a
72.Em connected
73state, while
74.Fn sendto ,
75.Fn sendmsg
76and
77.Fn sendmmsg
78may be used at any time.
79.Pp
80The address of the target is given by
81.Fa to
82with
83.Fa tolen
84specifying its size.
85The length of the message is given by
86.Fa len .
87If the message is too long to pass atomically through the
88underlying protocol, the error
89.Er EMSGSIZE
90is returned, and
91the message is not transmitted.
92.Pp
93The
94.Fn sendmmsg
95function sends multiple messages at a call.
96They are given by the
97.Fa msgvec
98vector along with
99.Fa vlen
100specifying the vector size.
101The number of octets sent per each message is placed in the
102.Fa msg_len
103field of each processed element of the vector after transmission.
104.Pp
105No indication of failure to deliver is implicit in a
106.Fn send .
107Locally detected errors are indicated by a return value of -1.
108.Pp
109If no messages space is available at the socket to hold
110the message to be transmitted, then
111.Fn send
112normally blocks, unless the socket has been placed in
113non-blocking I/O mode.
114The
115.Xr select 2
116system call may be used to determine when it is possible to
117send more data.
118.Pp
119The
120.Fa flags
121argument may include one or more of the following:
122.Bd -literal
123#define	MSG_OOB		0x00001 /* process out-of-band data */
124#define	MSG_DONTROUTE	0x00004 /* bypass routing, use direct interface */
125#define MSG_EOR		0x00008 /* data completes record */
126#define	MSG_EOF		0x00100 /* data completes transaction */
127#define	MSG_NOSIGNAL	0x20000 /* do not generate SIGPIPE on EOF */
128.Ed
129.Pp
130The flag
131.Dv MSG_OOB
132is used to send
133.Dq out-of-band
134data on sockets that support this notion (e.g.\&
135.Dv SOCK_STREAM ) ;
136the underlying protocol must also support
137.Dq out-of-band
138data.
139.Dv MSG_EOR
140is used to indicate a record mark for protocols which support the
141concept.
142.Dv MSG_EOF
143requests that the sender side of a socket be shut down, and that an
144appropriate indication be sent at the end of the specified data;
145this flag is only implemented for
146.Dv SOCK_STREAM
147sockets in the
148.Dv PF_INET
149protocol family.
150.Dv MSG_DONTROUTE
151is usually used only by diagnostic or routing programs.
152.Dv MSG_NOSIGNAL
153is used to prevent
154.Dv SIGPIPE
155generation when writing a socket that
156may be closed.
157.Pp
158See
159.Xr recv 2
160for a description of the
161.Fa msghdr
162structure and the
163.Fa mmsghdr
164structure.
165.Sh RETURN VALUES
166The
167.Fn send ,
168.Fn sendto
169and
170.Fn sendmsg
171calls
172return the number of octets sent.
173The
174.Fn sendmmsg
175call returns the number of messages sent.
176If an error occurred a value of -1 is returned.
177.Sh ERRORS
178The
179.Fn send
180and
181.Fn sendmmsg
182functions and
183.Fn sendto
184and
185.Fn sendmsg
186system calls
187fail if:
188.Bl -tag -width Er
189.It Bq Er EBADF
190An invalid descriptor was specified.
191.It Bq Er EACCES
192The destination address is a broadcast address, and
193.Dv SO_BROADCAST
194has not been set on the socket.
195.It Bq Er ENOTSOCK
196The argument
197.Fa s
198is not a socket.
199.It Bq Er EFAULT
200An invalid user space address was specified for an argument.
201.It Bq Er EMSGSIZE
202The socket requires that message be sent atomically,
203and the size of the message to be sent made this impossible.
204.It Bq Er EAGAIN
205The socket is marked non-blocking and the requested operation
206would block.
207.It Bq Er ENOBUFS
208The system was unable to allocate an internal buffer.
209The operation may succeed when buffers become available.
210.It Bq Er ENOBUFS
211The output queue for a network interface was full.
212This generally indicates that the interface has stopped sending,
213but may be caused by transient congestion.
214.It Bq Er EHOSTUNREACH
215The remote host was unreachable.
216.It Bq Er EISCONN
217A destination address was specified and the socket is already connected.
218.It Bq Er ECONNREFUSED
219The socket received an ICMP destination unreachable message
220from the last message sent.
221This typically means that the
222receiver is not listening on the remote port.
223.It Bq Er EHOSTDOWN
224The remote host was down.
225.It Bq Er ENETDOWN
226The remote network was down.
227.It Bq Er EADDRNOTAVAIL
228The process using a
229.Dv SOCK_RAW
230socket was jailed and the source
231address specified in the IP header did not match the IP
232address bound to the prison.
233.It Bq Er EPIPE
234The socket is unable to send anymore data
235.Dv ( SBS_CANTSENDMORE
236has been set on the socket).
237This typically means that the socket
238is not connected.
239.El
240.Sh SEE ALSO
241.Xr fcntl 2 ,
242.Xr getsockopt 2 ,
243.Xr recv 2 ,
244.Xr select 2 ,
245.Xr socket 2 ,
246.Xr write 2
247.Sh HISTORY
248The
249.Fn send
250function appeared in
251.Bx 4.2 .
252The
253.Fn sendmmsg
254function appeared in
255.Fx 11.0 .
256.Sh BUGS
257Because
258.Fn sendmsg
259does not necessarily block until the data has been transferred, it
260is possible to transfer an open file descriptor across an
261.Dv AF_UNIX
262domain socket
263(see
264.Xr recv 2 ) ,
265then
266.Fn close
267it before it has actually been sent, the result being that the receiver
268gets a closed file descriptor.
269It is left to the application to
270implement an acknowledgment mechanism to prevent this from happening.
271