THR_SET_NAME(2)

💖 THR_SET_NAME(2) 💖

okay bestie, so this is a system call — from the System Calls Manual — and it's literally called thr_set_name. Yes, that's the whole vibe: it sets the user-visible thread name. 🎀

---

✨ NAME ✨

thr_set_name — set user-visible thread name 🏷️

---

📚 LIBRARY 📚

Standard C Library (libc, -lc) 🫶

---

🌸 SYNOPSIS 🌸

#include <sys/thr.h>

int
thr_set_name(long id, const char *name);

---

💅 DESCRIPTION 💅

so basically, the thr_set_name() system call sets the user-visible name for the thread with the identifier id — in the current process, no cap — to the NUL-terminated string name. ✨

and listen. the name gets silently truncated to fit into a buffer of MAXCOMLEN + 1 bytes. no error, no warning, no drama — it just gets cut off. 💀 so if you name your thread something iconic and long, only the beginning survives. keep that in mind, bestie.

where does the name show up, you ask? literally everywhere, it's giving main character energy: 👑

• the output of ps(1) and top(1) commands
• the kernel debuggers 🐛
• the kernel tracing facility outputs
• userland debuggers and program core files — as notes

---

🔥 RETURN VALUES 🔥

if it slays: thr_set_name() returns zero. 🎉

if it does not slay: -1 is returned, and errno is set to indicate the error. 😭

---

🚨 ERRORS 🚨

the thr_set_name() system call may return the following errors:

• [EFAULT] — the memory pointed to by the name argument is not valid. 🙈
• [ESRCH] — the thread with the identifier id does not exist in the current process. 💀

---

👀 SEE ALSO 👀

ps(1), thr_exit(2), thr_kill(2), thr_kill2(2), thr_new(2), thr_self(2), _umtx_op(2), pthread_set_name_np(3), ddb(4), ktr(9) 🦋

---

⭐ STANDARDS ⭐

the thr_set_name() system call is non-standard — periodt. it's used by the 1:1 Threading Library (libthr, -lthr). 🌈

---

and that's the whole page, bestie!! 💜 this one shipped from Debian, dated December 2, 2016 — so like, a vintage icon at this point. go name ur threads something cute 🎀✨