DMMP_CONTEXT_LOG_PRIORITY_GET(3)

πŸ“¦
version 0.15.1 Β· 3 versions
, in arch rolling, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ’– dmmp_context_log_priority_get β€” get log priority πŸ’–

okay bestie, so this is part of the Device Mapper Multipath API β€” aka the libdmmp manual, and today we're looking at dmmp_context_log_priority_get(3). it's literally just "hey, what log priority am i on right now?" and honestly? iconic. πŸŽ€


✨ SYNOPSIS ✨

int dmmp_context_log_priority_get (struct dmmp_context *ctx);

🌸 ARGUMENTS 🌸

  • ctx β€” a pointer to your struct dmmp_context. and listen, if this pointer is NULL? yeah no, your program is getting terminated by assert. not a vibe check you wanna fail. πŸ’€

πŸ¦‹ DESCRIPTION πŸ¦‹

it retrieves the current log priority. that's the whole thing, she's simple and she serves. 🫢

the valid log priority values are:

  • DMMP_LOG_PRIORITY_ERROR β€” 3
  • DMMP_LOG_PRIORITY_WARNING β€” 4
  • DMMP_LOG_PRIORITY_INFO β€” 5
  • DMMP_LOG_PRIORITY_DEBUG β€” 7
yes bestie, those numbers are literally the real ones. 3, 4, 5, 7. no 6. we don't talk about 6. πŸ™ˆ

πŸ’… RETURN πŸ’…

int β€” the log priority. that's it, that's the tea. ⭐


mwah, that's the whole page, go off and log responsibly bestie πŸ’œ

this one's from the libdmmp manual, dated June 2025, filed under dmmp_context_log_priority_get, and the running header vibe was dmmp_...ty_get(3) β€” yeah, they really did just cut the middle out of the name, periodt. 😭✨