SCTP_PEELOFF(2)

✨ NAME ✨

SCTP_PEELOFF(2) is a System Calls Manual page, and the name is literally the plot: sctp_peeloff — detach an association from a one-to-many socket to its own fd. bestie, that’s the whole assignment. 💅

🎀 LIBRARY 🎀

It comes courtesy of the Standard C Library (libc, -lc) — iconic, no notes. 💖

💅 SYNOPSIS 💅

#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/sctp.h>

int
sctp_peeloff(int s, sctp_assoc_t id);

🦋 DESCRIPTION 🦋

Okay so sctp_peeloff() is a system call, and what it does is attempt to detach the association specified by id into its own separate socket. That’s it, that’s the vibe: one association gets its own solo fd. 🦋

🔥 RETURN VALUES 🔥

On success, the call returns the new socket descriptor — slay. On failure, it returns -1. Periodt. 🔥

💀 ERRORS 💀

sctp_peeloff() can return the following errors, and we’re listing every single one:

• [ENOTCONN] — the id given to the call does not map to a valid association.
• [E2BIG] — the size of the address list exceeds the amount of data provided.
• [EBADF] — the argument s is not a valid descriptor.
• [ENOTSOCK] — the argument s is not a socket.

👑 SEE ALSO 👑

Go read sctp(4) next, bestie — it’s the linked lore. 👑

🌈 STANDARDS 🌈

Standards check: the sctp_peeloff() function conforms to RFC 6458. we love a compliant icon. 🌈

xoxo, Debian 💖 — February 2, 2024 — SCTP_PEELOFF(2) out 🎀