explain_ge...ity_or_die(3)

💖 explain_getpriority_or_die — the group chat manual (3) 💖

okay so bestie, welcome to the explain_ge...ity_or_die(3) page, filed under Library Functions Manual and living rent-free in your terminal. it's giving "short but mighty" and honestly? we're obsessed. 💅

---

✨ NAME ✨

explain_getpriority_or_die — get program scheduling priority and report errors 🦋

---

✨ SYNOPSIS ✨

#include <libexplain/getpriority.h>
int explain_getpriority_or_die(int which, int who);
int explain_getpriority_on_error(int which, int who);

two icons, one header file. slay. ✨

---

✨ DESCRIPTION ✨

so, explain_getpriority_or_die is the bestie that calls the getpriority(2) system call for you. but here's the tea ☕ — if it fails, it prints an explanation to stderr, grabbed straight from the explain_getpriority(3) function, and then the process terminates by calling exit(EXIT_FAILURE). like, it does not come back. it's gone. periodt. 💀

meanwhile explain_getpriority_on_error is the softer sibling 🌸 — it also calls getpriority(2), and on failure it also prints an explanation to stderr (same source, explain_getpriority(3)), BUT it still returns to the caller. no dramatic exit. it stays. 🫶

now the arguments, because we don't gatekeep:

• which — the which, exactly as to be passed to the getpriority(2) system call. yes literally exactly. don't get creative. 🎀
• who — the who, exactly as to be passed to the getpriority(2) system call. same energy. exactly. 🌈

---

✨ RETURN VALUE ✨

explain_getpriority_or_die only returns on success — see getpriority(2) for more info. on failure? it prints an explanation and exits. it does not return. not even a little. 🙈

explain_getpriority_on_error always returns the value returned by the wrapped getpriority(2) system call. always. every time. 💖

---

✨ EXAMPLE ✨

explain_getpriority_or_die is intended to be used in a fashion similar to the following example:

int result = explain_getpriority_or_die(which, who);

that's it. that's the whole vibe. copy it, ship it, main character energy. 👑

---

✨ SEE ALSO ✨

• getpriority(2) — get program scheduling priority 🌟
• explain_getpriority(3) — explain getpriority(2) errors 🔥
• exit(2) — terminate the calling process 💀

---

✨ COPYRIGHT ✨

libexplain version 1.4 Copyright (C) 2013 Peter Miller

---

and that's the whole page, bestie 🎀 this was explain_ge...ity_or_die(3) from Library Functions Manual, brought to you by libexplain version 1.4, Copyright (C) 2013 Peter Miller — ily, go call getpriority(2) responsibly, and don't forget to vibe check your which and who before you pass them. mwah. 💜🦋✨