ACCEPT(3P)

💖 ACCEPT(3P) — POSIX Programmer's Manual 💖

okay bestie, so this is ACCEPT(3P), it lives in the POSIX Programmer's Manual, and we're gonna get you fluent in it. pull up a chair, grab a strawberry 🍓, let's go.

---

🌸 PROLOG 🌸

So real talk first: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ — so if you're on Linux, go consult the corresponding Linux manual page for the deets on Linux behavior. OR the interface might not even be implemented on Linux at all. it's giving "check your local listings" ✨

---

✨ NAME ✨

accept — accept a new connection on a socket 🫶

---

🎀 SYNOPSIS 🎀

#include <sys/socket.h>

int accept(int socket, struct sockaddr *restrict address,
    socklen_t *restrict address_len);

like yes that's the whole vibe, three args, we'll get to them 💅

---

💅 DESCRIPTION 💅

So what does accept() actually do? Bestie. It:

• extracts the first connection on the queue of pending connections 🔥
• creates a new socket with the same socket type, protocol and address family as the specified socket
• allocates a new file descriptor for that socket

and that file descriptor is allocated as described in Section 2.14, File Descriptor Allocation. periodt.

The accept() function takes the following arguments:

• socket — specifies a socket that was created with socket(), has been bound to an address with bind(), and has issued a successful call to listen(). (so like, it's already been through the whole glow-up pipeline 👑)
• address — either a null pointer, or a pointer to a sockaddr structure where the address of the connecting socket shall be returned.
• 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. she does double duty, iconic 💅

If address is not a null pointer, the address of the peer for the accepted connection shall be stored in the sockaddr structure pointed to by address, and the length of this address shall be stored in the object pointed to by address_len.

If the actual length of the address is greater than the length of the supplied sockaddr structure, the stored address shall be truncated. 😭 rude but true

If the protocol permits connections by unbound clients, and the peer is not bound, then the value stored in the object pointed to by address is unspecified. like, unspecified unspecified. don't come for her.

🫧 Now the blocking tea: if the listen queue is empty of connection requests and O_NONBLOCK is not set on the file descriptor for the socket, accept() shall block until a connection is present. But if the listen() queue is empty of connection requests and O_NONBLOCK is set on the file descriptor for the socket, accept() shall fail and set errno to [EAGAIN] or [EWOULDBLOCK]. no cap.

And the biggest plot twist: the accepted socket cannot itself accept more connections. The original socket remains open and can accept more connections. so the OG socket is the one with main character energy, the new one is just here for the vibes 🌈

---

🔥 RETURN VALUE 🔥

Upon successful completion, accept() shall return the non-negative file descriptor of the accepted socket. 🎉

Otherwise, -1 shall be returned, errno shall be set to indicate the error, and any object pointed to by address_len shall remain unchanged. (so at least she doesn't ghost your data ✨)

---

💀 ERRORS 💀

The accept() function shall fail if:

• EAGAIN or EWOULDBLOCK — O_NONBLOCK is set for the socket file descriptor and no connections are present to be accepted.
• EBADF — the socket argument is not a valid file descriptor.
• ECONNABORTED — a connection has been aborted.
• EINTR — the accept() function was interrupted by a signal that was caught before a valid connection arrived.
• EINVAL — the socket is not accepting connections.
• EMFILE — all file descriptors available to the process are currently open.
• ENFILE — the maximum number of file descriptors in the system are already open.
• ENOBUFS — no buffer space is available.
• ENOMEM — there was insufficient memory available to complete the operation.
• ENOTSOCK — the socket argument does not refer to a socket.
• EOPNOTSUPP — the socket type of the specified socket does not support accepting connections.

The accept() function may fail if:

• EPROTO — a protocol error has occurred; for example, the STREAMS protocol stack has not been initialized.

The following sections are informative. 👀 (so like, cute bonus content, not the law)

---

🌈 EXAMPLES 🌈

None.

she said no examples. and honestly? respect. 🙈

---

🦋 APPLICATION USAGE 🦋

When a connection is available, select() indicates that the file descriptor for the socket is ready for reading. that's your lil heads-up notification bestie 🔔

---

⭐ RATIONALE ⭐

None.

---

🧚 FUTURE DIRECTIONS 🧚

None.

---

💜 SEE ALSO 💜

• Section 2.14, File Descriptor Allocation
• bind()
• connect()
• listen()
• socket()
• The Base Definitions volume of POSIX.1‐2017, <sys_socket.h>

---

👑 COPYRIGHT 👑

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 .

---

that's the whole page bestie, you ate it 💅✨

IEEE/The Open Group — 2017 — ACCEPT(3P) 🎀 bye ily, go accept some connections 🫶