pthread_mu...setkind_np(3)

💅 pthread_mu...setkind_np(3) 💅

okay bestie, so this page is straight out of the Library Functions Manual, and it's literally titled pthread_mu...setkind_np(3). yes the name is truncated, that's just how it is, we move. 🫶

---

✨ NAME ✨

pthread_mutexattr_setkind_np, pthread_mutexattr_getkind_np — deprecated mutex creation attributes 😭

like... they still exist, but they're giving retirement home energy. pls read on.

---

🌸 SYNOPSIS 🌸

#include <pthread.h>

int pthread_mutexattr_setkind_np(pthread_mutexattr_t *attr, int kind);
int pthread_mutexattr_getkind_np(const pthread_mutexattr_t *attr,
                                 int *kind);

one sets, one gets. classic duo. dynamic duo. 👑

---

🦋 DESCRIPTION 🦋

so here's the tea, and it's not the fun kind: these functions are deprecated. 🫠

instead, you want to use pthread_mutexattr_settype(3) and pthread_mutexattr_gettype(3). literally just go use those, they're the glow-up versions.

no cap, if you're writing new code and you reach for these, put your hand down. settype and gettype are right there bestie!! 🙈

---

💖 RETURN VALUE 💖

• pthread_mutexattr_getkind_np() — always returns 0. always. it's an absolute icon of consistency, it does not miss. 💅
• pthread_mutexattr_setkind_np() — returns 0 when it succeeds, and a non-zero error code when it errors out. so 0 = slay, non-zero = uh oh. 😭

---

🔥 ERRORS 🔥

when pthread_mutexattr_setkind_np() messes up, it hands you back this error code:

• EINVAL — kind is neither PTHREAD_MUTEX_FAST_NP nor PTHREAD_MUTEX_RECURSIVE_NP nor PTHREAD_MUTEX_ERRORCHECK_NP. in other words: you gave it a vibe it does not recognise, and it is not about to fw that. 💀

---

🌈 SEE ALSO 🌈

• pthread_mutexattr_settype(3)
• pthread_mutexattr_gettype(3)

---

🎀 bye bestie 🎀

this was brought to you by Linux man-pages 6.20, dated 2025-05-17, and the title card said pthread_mu...setkind_np(3) the whole time. now go call pthread_mutexattr_settype(3) instead, ily, mwah. 💜✨