#include <sys/types.h>
#include <sys/socket.h>
int send(int s, const void *msg, size_t len,
int flags);
int sendto(int s, const void *msg, size_t len,
int flags, const struct sockaddr *to, socklen_t tolen);
int sendmsg(int s, const struct msghdr *msg,
int flags);
Send,
sendto,
and
sendmsg
are used to transmit a message to another socket.
Send
may be used only when the socket is in a
connected
state, while
sendto
and
sendmsg
may be used at any time.
The address of the target is given by
to
with
tolen
specifying its size. The length of the message is given by
len.
If the message is too long to pass atomically through the
underlying protocol, the error
EMSGSIZE
is returned, and the message is not transmitted.
No indication of failure to deliver is implicit in a
send.
Locally detected errors are indicated by a return value of -1.
When the message does not fit into the send buffer of the socket,
send
normally blocks, unless the socket has been placed in non-blocking I/O
mode. In non-blocking mode it would return
EAGAIN
in this case.
The
select(2)
call may be used to determine when it is possible to send more data.
The
flags
parameter is a flagword and can contain the following flags:
- MSG_OOB
-
Sends
out-of-band
data on sockets that support this notion (e.g.
SOCK_STREAM);
the underlying protocol must also support
out-of-band
data.
- MSG_DONTROUTE
-
Dont't use a gateway to send out the packet, only send to hosts on
directly connected networks. This is usually used only
by diagnostic or routing programs. This is only defined for protocol
families that route; packet sockets don't.
- MSG_DONTWAIT
-
Enables non-blocking operation; if the operation would block,
EAGAIN
is returned (this can also be enabled using the
O_NONBLOCK
with the
F_SETFL
fcntl(2)).
- MSG_NOSIGNAL
-
Requests not to send
SIGPIPE
on errors on stream oriented sockets when the other end breaks the
connection. The
EPIPE
error is still returned.
- MSG_CONFIRM (Linux 2.3+ only)
-
Tell the link layer that forward process happened: you got a successful
reply from the other side. If the link layer doesn't get this
it'll regularly reprobe the neighbour (e.g. via a unicast ARP).
Only valid on
SOCK_DGRAM
and
SOCK_RAW
sockets and currently only implemented for IPv4 and IPv6. See