LOC_GET_LOG_PRIORITY(3)
π
LOC_GET_LOG_PRIORITY(3) β the loc_get_log_priority tea β
okay so bestie, welcome to the libloc section 3 manual, page LOC_GET_LOG_PRIORITY(3). yeah the header literally just says that twice, we love a self-referential icon π
β¨ NAME β¨
loc_get_log_priority β grabs the log level of a libloc context π
basically: you got a context, it's got a log priority, this function tells you what it is. that's the whole vibe.
πΈ SYNOPSIS πΈ
#include <libloc/libloc.h>
int loc_get_log_priority(struct loc_ctx* ctx);
one include, one function, zero drama. the way that int just returns things π«Ά
π¦ DESCRIPTION π¦
So. You call this bad boy and it returns the log priority of the given context. That's it, that's the function. Main character energy, honestly.
The integer it hands back is a valid syslog log level, exactly as defined in syslog(3) β so like, the real deal, not some made-up number. iykyk π₯
And the default value? LOG_ERR. That's the starting point before anybody messes with it, no cap.
lowkey the chillest function in the whole library and I'm obsessed with her for it π
π SEE ALSO π
libloc(3)β go read the parent page bestie, it's giving context (literally) π
π AUTHORS π
Michael Tremer β an absolute legend, we stan π
okay so that's the whole page β and for the sign-off, the footer is honestly just LOC_GET_LOG_PRIORITY(3) all over again π no version string, no date stamp, nothing extra to report. so here's your cute little goodbye: go forth, check your log priority, and slay β¨ππ¦
π¦ where this page comes from
- ubuntu stonking: libloc-dev 0.9.19-1build1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms