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.\" 3. 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 4, 2019 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/socket.h 44.Ft ssize_t 45.Fn send "int s" "const void *msg" "size_t len" "int flags" 46.Ft ssize_t 47.Fn sendto "int s" "const void *msg" "size_t len" "int flags" "const struct sockaddr *to" "socklen_t tolen" 48.Ft ssize_t 49.Fn sendmsg "int s" "const struct msghdr *msg" "int flags" 50.Ft ssize_t 51.Fn sendmmsg "int s" "struct mmsghdr * restrict msgvec" "size_t vlen" "int flags" 52.Sh DESCRIPTION 53The 54.Fn send 55and 56.Fn sendmmsg 57functions, 58and 59.Fn sendto 60and 61.Fn sendmsg 62system calls 63are used to transmit one or more messages (with the 64.Fn sendmmsg 65call) to 66another socket. 67The 68.Fn send 69function 70may be used only when the socket is in a 71.Em connected 72state, while 73.Fn sendto , 74.Fn sendmsg 75and 76.Fn sendmmsg 77may be used at any time. 78.Pp 79The address of the target is given by 80.Fa to 81with 82.Fa tolen 83specifying its size. 84The length of the message is given by 85.Fa len . 86If the message is too long to pass atomically through the 87underlying protocol, the error 88.Er EMSGSIZE 89is returned, and 90the message is not transmitted. 91.Pp 92The 93.Fn sendmmsg 94function sends multiple messages at a call. 95They are given by the 96.Fa msgvec 97vector along with 98.Fa vlen 99specifying the vector size. 100The number of octets sent per each message is placed in the 101.Fa msg_len 102field of each processed element of the vector after transmission. 103.Pp 104No indication of failure to deliver is implicit in a 105.Fn send . 106Locally detected errors are indicated by a return value of -1. 107.Pp 108If no messages space is available at the socket to hold 109the message to be transmitted, then 110.Fn send 111normally blocks, unless the socket has been placed in 112non-blocking I/O mode. 113The 114.Xr select 2 115system call may be used to determine when it is possible to 116send more data. 117.Pp 118The 119.Fa flags 120argument may include one or more of the following: 121.Bd -literal 122#define MSG_OOB 0x00001 /* process out-of-band data */ 123#define MSG_DONTROUTE 0x00004 /* bypass routing, use direct interface */ 124#define MSG_EOR 0x00008 /* data completes record */ 125#define MSG_DONTWAIT 0x00080 /* do not block */ 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. 142The 143.Dv MSG_DONTWAIT 144flag request the call to return when it would block otherwise. 145.Dv MSG_EOF 146requests that the sender side of a socket be shut down, and that an 147appropriate indication be sent at the end of the specified data; 148this flag is only implemented for 149.Dv SOCK_STREAM 150sockets in the 151.Dv PF_INET 152protocol family. 153.Dv MSG_DONTROUTE 154is usually used only by diagnostic or routing programs. 155.Dv MSG_NOSIGNAL 156is used to prevent 157.Dv SIGPIPE 158generation when writing a socket that 159may be closed. 160.Pp 161See 162.Xr recv 2 163for a description of the 164.Fa msghdr 165structure and the 166.Fa mmsghdr 167structure. 168.Sh RETURN VALUES 169The 170.Fn send , 171.Fn sendto 172and 173.Fn sendmsg 174calls 175return the number of octets sent. 176The 177.Fn sendmmsg 178call returns the number of messages sent. 179If an error occurred a value of -1 is returned. 180.Sh ERRORS 181The 182.Fn send 183and 184.Fn sendmmsg 185functions and 186.Fn sendto 187and 188.Fn sendmsg 189system calls 190fail if: 191.Bl -tag -width Er 192.It Bq Er EBADF 193An invalid descriptor was specified. 194.It Bq Er EACCES 195The destination address is a broadcast address, and 196.Dv SO_BROADCAST 197has not been set on the socket. 198.It Bq Er ENOTSOCK 199The argument 200.Fa s 201is not a socket. 202.It Bq Er EFAULT 203An invalid user space address was specified for an argument. 204.It Bq Er EMSGSIZE 205The socket requires that message be sent atomically, 206and the size of the message to be sent made this impossible. 207.It Bq Er EAGAIN 208The socket is marked non-blocking, or 209.Dv MSG_DONTWAIT 210is specified, and the requested operation would block. 211.It Bq Er ENOBUFS 212The system was unable to allocate an internal buffer. 213The operation may succeed when buffers become available. 214.It Bq Er ENOBUFS 215The output queue for a network interface was full. 216This generally indicates that the interface has stopped sending, 217but may be caused by transient congestion. 218.It Bq Er EHOSTUNREACH 219The remote host was unreachable. 220.It Bq Er EISCONN 221A destination address was specified and the socket is already connected. 222.It Bq Er ECONNREFUSED 223The socket received an ICMP destination unreachable message 224from the last message sent. 225This typically means that the 226receiver is not listening on the remote port. 227.It Bq Er EHOSTDOWN 228The remote host was down. 229.It Bq Er ENETDOWN 230The remote network was down. 231.It Bq Er EADDRNOTAVAIL 232The process using a 233.Dv SOCK_RAW 234socket was jailed and the source 235address specified in the IP header did not match the IP 236address bound to the prison. 237.It Bq Er EPIPE 238The socket is unable to send anymore data 239.Dv ( SBS_CANTSENDMORE 240has been set on the socket). 241This typically means that the socket 242is not connected. 243.El 244.Sh SEE ALSO 245.Xr fcntl 2 , 246.Xr getsockopt 2 , 247.Xr recv 2 , 248.Xr select 2 , 249.Xr socket 2 , 250.Xr write 2 , 251.Xr CMSG_DATA 3 252.Sh HISTORY 253The 254.Fn send 255function appeared in 256.Bx 4.2 . 257The 258.Fn sendmmsg 259function appeared in 260.Fx 11.0 . 261.Sh BUGS 262Because 263.Fn sendmsg 264does not necessarily block until the data has been transferred, it 265is possible to transfer an open file descriptor across an 266.Dv AF_UNIX 267domain socket 268(see 269.Xr recv 2 ) , 270then 271.Fn close 272it before it has actually been sent, the result being that the receiver 273gets a closed file descriptor. 274It is left to the application to 275implement an acknowledgment mechanism to prevent this from happening. 276