setsid(2)

💖 setsid(2) 💖

okay bestie, welcome to the System Calls Manual section, we're talking about setsid today and honestly? it's lowkey iconic. sit down, grab a strawberry, let's get into it. 🍓

---

✨ NAME ✨

setsid — creates a session and sets the process group ID

📚 LIBRARY 📚

Standard C library (libc, link with -lc)

🌸 SYNOPSIS 🌸

#include <unistd.h>

pid_t setsid(void);

💅 DESCRIPTION 💅

okay so here's the tea: setsid() creates a new session — but only if the calling process is not a process group leader. that's the vibe check. 🫶

and then boom: the calling process becomes the leader of the new session. like, its session ID gets set to the same value as its process ID. no cap. 🎀

AND that's not even all of it — the calling process ALSO becomes the leader of a brand new process group inside that new session. meaning its process group ID is also made the same as its process ID. it's giving main character energy fr fr. 👑

so after all that: the calling process is the only process in the new process group, and the only process in the new session. literally just them. alone. thriving. ✨

initially, the new session has no controlling terminal. if you wanna know the details of how a session actually acquires a controlling terminal, go read credentials(7) — that's where the lore lives. 📖

🔥 RETURN VALUE 🔥

on success, setsid() returns the (new) session ID of the calling process. slay. 💖

on error, it returns (pid_t) -1, and errno gets set to tell you what went wrong. 💀

😭 ERRORS 😭

• EPERM — this one means the process group ID of any process equals the PID of the calling process. so like, in particular? setsid() fails if the calling process is already a process group leader. no getting around it, bestie, it's just gonna fail. 🙈

⭐ STANDARDS ⭐

POSIX.1-2024. periodt.

🦋 HISTORY 🦋

POSIX.1-2001, SVr4. a classic, an OG, we respect the elders. 💜

👑 NOTES 👑

a child created via fork(2) inherits its parent's session ID. and that session ID is preserved across an execve(2). good to know, right? 🌈

---

🧚 what even IS a process group leader 🧚

okay so a process group leader is a process whose process group ID equals its PID. simple as that.

now, why do we disallow a process group leader from calling setsid()? because if a process group leader could yeet itself into a new session while all the other processes in its process group stayed behind in the original session, that would break the strict two-level hierarchy of sessions and process groups. and we do not break the hierarchy. that's the whole point. 💅

so if you need to be sure that setsid() will succeed? here's the move: call fork(2), have the parent call _exit(3), and let the child — which by definition can't be a process group leader — call setsid(). iconic workaround. 🎀

---

🚨 terminal drama 🚨

if a session has a controlling terminal, and the CLOCAL flag for that terminal is not set, and a terminal hangup occurs, then the session leader gets sent a SIGHUP signal. 😭

and if a process that is a session leader terminates, then a SIGHUP signal is sent to each process in the foreground process group of the controlling terminal. that's a lot of sighups bestie, everyone's getting one. 💀

🌟 SEE ALSO 🌟

• setsid(1)
• getsid(2)
• setpgid(2)
• setpgrp(2)
• tcgetsid(3)
• credentials(7)
• sched(7)

---

and that's the whole page, bestie!! 💖✨🎀🦋🌸

this was brought to you by Linux man-pages 6.20, dated 2026-06-05. drink some water, call your session leader, bye!! 🫶👑💅