PR_SET_CHILD_SUBREAPER(2const)

💖 PR_SET_CHILD_SUBREAPER — the prctl(2const) page, bestie edition 💖

okay so you found PR_SET_CHILD_SUBREAPER(2const) and honestly? iconic of you. this lives in the prctl corner of the Linux manual, and it's all about making your process the certified mom friend of its whole little process family tree. let's get into it. 🫶

---

✨ LIBRARY ✨

Standard C library (libc, -lc) — the usual, nothing spicy here. 💅

---

🌸 SYNOPSIS 🌸

#include <linux/prctl.h>  /* Definition of PR_* constants */
#include <sys/prctl.h>

int prctl(PR_SET_CHILD_SUBREAPER, long set);

---

🎀 DESCRIPTION 🎀

so here's the tea. if set is nonzero, you're setting the "child subreaper" attribute on the calling process. if set is zero, you're unsetting it. that's the whole toggle. simple, clean, slay. ✨

now what even is a subreaper, you ask? a subreaper literally fulfills the role of init(1) for its descendant processes. like, it's stepping into the main character role. 👑

here's how it goes down: when a process becomes orphaned (meaning its immediate parent terminates — sad, tragic, we've all been there 😭), that process gets reparented to the nearest still living ancestor subreaper.

and then? every subsequent call to getppid(2) inside that orphaned process will now return the PID of the subreaper process. not the original parent, bestie. the subreaper. and when the orphan finally terminates, it's the subreaper process that receives the SIGCHLD signal 🔔 and gets to call wait(2) on the process to discover its termination status. so the subreaper always knows what happened. no cap.

important detail tho: the setting of the "child subreaper" attribute is not inherited by children created by fork(2) and clone(2). the vibes do not pass down, fr fr. but the setting is preserved across execve(2). so it survives the transformation. 💫

why would you even want this? establishing a subreaper process is useful in session management frameworks, where a hierarchical group of processes is managed by a subreaper process that needs to be informed when one of the processes— for example, a double-forked daemon — terminates (perhaps so that it can restart that process). and some init(1) frameworks (e.g., systemd(1)) employ a subreaper process for similar reasons. so yes, this is real production energy, not just a cute experiment. 🔥

---

💜 RETURN VALUE 💜

• on success, 0 is returned. 🎉
• on error, -1 is returned, and errno is set to indicate the error. 🙈

---

🌈 STANDARDS 🌈

Linux. that's it. that's the standard. 🐧

---

⭐ HISTORY ⭐

Linux 3.4. vintage-ish, but still eating. 👑

---

🦋 SEE ALSO 🦋

• prctl(2)
• PR_GET_CHILD_SUBREAPER(2const)

---

and that's the whole page, bestie!! this came from Linux man-pages 6.20, dated 2026-02-08 — so when you cite your sources, you cite them correctly, periodt. 💖✨ go forth and subreap responsibly 🎀