RECVFROM(3POSIX)

πŸ’– PROLOG πŸ’–

Okay bestie, before we even get into it: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so like, go check the corresponding Linux manual page for the deets on Linux behavior, fr), or the interface might not even be implemented on Linux at all. πŸ™ˆ Not every system is gonna have it, and that's just the vibe sometimes.


✨ NAME ✨

recvfrom β€” receive a message from a socket πŸ’Œ


πŸŽ€ SYNOPSIS πŸŽ€

#include <sys/socket.h>

ssize_t recvfrom(int socket, void *restrict buffer, size_t length,
    int flags, struct sockaddr *restrict address,
    socklen_t *restrict address_len);

πŸ¦‹ DESCRIPTION πŸ¦‹

So the recvfrom() function shall receive a message from a connection-mode or connectionless-mode socket. It's normally used with connectionless-mode sockets, because it lets your application retrieve the source address of the data it just received. It's giving "who even sent me this" energy, and it answers that question. πŸ‘‘

The recvfrom() function takes the following arguments:

  • socket β€” Specifies the socket file descriptor. Your lil ticket to the socket, basically.
  • buffer β€” Points to the buffer where the message should be stored. This is where the message goes to live. 🏠
  • length β€” Specifies the length in bytes of the buffer pointed to by the buffer argument. Know your limits bestie.
  • flags β€” Specifies the type of message reception. Values of this argument are formed by logically OR'ing zero or more of the following values:
    • MSG_PEEK β€” Peeks at an incoming message. The data is treated as unread and the next recvfrom() or similar function shall still return this data. It's the "just looking, not touching" option, no cap. πŸ‘€
    • MSG_OOB β€” Requests out-of-band data. The significance and semantics of out-of-band data are protocol-specific. Every protocol does its own thing with this one, iykyk.
    • MSG_WAITALL β€” On SOCK_STREAM sockets this requests that the function block until the full amount of data can be returned. But heads up: the function may return the smaller amount of data if the socket is a message-based socket, if a signal is caught, if the connection is terminated, if MSG_PEEK was specified, or if an error is pending for the socket. So it's "wait for all" with like, several asterisks. 😭
  • address β€” A null pointer, or points to a sockaddr structure in which the sending address is to be stored. The length and format of the address depend on the address family of the socket. πŸ’…
  • address_len β€” Either a null pointer, if address is a null pointer, or a pointer to a socklen_t object which on input specifies the length of the supplied sockaddr structure, and on output specifies the length of the stored address. It's a two-way street, it takes info in and gives info out. 🌈

The recvfrom() function shall return the length of the message written to the buffer pointed to by the buffer argument. For message-based sockets, such as SOCK_RAW, SOCK_DGRAM, and SOCK_SEQPACKET, the entire message shall be read in a single operation. If a message is too long to fit in the supplied buffer, and MSG_PEEK is not set in the flags argument, the excess bytes shall be discarded β€” gone, deleted, not coming back, so size your buffer accordingly bestie. πŸ’€ For stream-based sockets, such as SOCK_STREAM, message boundaries shall be ignored. In this case, data shall be returned to the user as soon as it becomes available, and no data shall be discarded.

If the MSG_WAITALL flag is not set, data shall be returned only up to the end of the first message.

Not all protocols provide the source address for messages. If the address argument is not a null pointer and the protocol provides the source address of messages, the source address of the received message shall be stored in the sockaddr structure pointed to by the address argument, and the length of this address shall be stored in the object pointed to by the address_len argument.

If the actual length of the address is greater than the length of the supplied sockaddr structure, the stored address shall be truncated. Snip snip. βœ‚οΈ

If the address argument is not a null pointer and the protocol does not provide the source address of messages, the value stored in the object pointed to by address is unspecified. Yeah. Unspecified. We don't know what's in there, nobody knows, don't look at it. πŸ™ˆ

If no messages are available at the socket and O_NONBLOCK is not set on the socket's file descriptor, recvfrom() shall block until a message arrives. Just vibing. Waiting. Patiently. 🧘 If no messages are available at the socket and O_NONBLOCK is set on the socket's file descriptor, recvfrom() shall fail and set errno to [EAGAIN] or [EWOULDBLOCK].


πŸ”₯ RETURN VALUE πŸ”₯

Upon successful completion, recvfrom() shall return the length of the message in bytes. If no messages are available to be received and the peer has performed an orderly shutdown, recvfrom() shall return 0. Otherwise, the function shall return -1 and set errno to indicate the error. Simple as that. ✨


πŸ’€ ERRORS πŸ’€

The recvfrom() function shall fail if:

  • EAGAIN or EWOULDBLOCK β€” The socket's file descriptor is marked O_NONBLOCK and no data is waiting to be received; or MSG_OOB is set and no out-of-band data is available and either the socket's file descriptor is marked O_NONBLOCK or the socket does not support blocking to await out-of-band data.
  • EBADF β€” The socket argument is not a valid file descriptor.
  • ECONNRESET β€” A connection was forcibly closed by a peer. Rude, honestly. 😀
  • EINTR β€” A signal interrupted recvfrom() before any data was available.
  • EINVAL β€” The MSG_OOB flag is set and no out-of-band data is available.
  • ENOTCONN β€” A receive is attempted on a connection-mode socket that is not connected.
  • ENOTSOCK β€” The socket argument does not refer to a socket.
  • EOPNOTSUPP β€” The specified flags are not supported for this socket type.
  • ETIMEDOUT β€” The connection timed out during connection establishment, or due to a transmission timeout on active connection.

The recvfrom() function may fail if:

  • EIO β€” An I/O error occurred while reading from or writing to the file system.
  • ENOBUFS β€” Insufficient resources were available in the system to perform the operation.
  • ENOMEM β€” Insufficient memory was available to fulfill the request.

The following sections are informative. (Which is fancy-speak for "this is context, not law," bestie.)


🌸 EXAMPLES 🌸

None. Nada. Zero examples, we're keeping it mysterious. πŸ’…


πŸ’œ APPLICATION USAGE πŸ’œ

The select() and poll() functions can be used to determine when data is available to be received. So like, if you don't wanna just sit there blocking forever, those are your girls. 🫢


⭐ RATIONALE ⭐

None. Nothing to justify here, it just is what it is.


πŸŽ€ FUTURE DIRECTIONS πŸŽ€

None. The future is... unspecified. (Fitting, honestly.)


πŸ‘‘ SEE ALSO πŸ‘‘

poll(), pselect(), read(), recv(), recvmsg(), send(), sendmsg(), sendto(), shutdown(), socket(), write()

The Base Definitions volume of POSIX.1‐2017, <sys_socket.h>


Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .


Okay that's the whole page bestie, you made it to the end, iconic behavior honestly. This one's brought to you by IEEE/The Open Group, dated 2017, and it lives under the name RECVFROM(3POSIX). Go forth and receive your messages. πŸ’…βœ¨πŸ¦‹