SASL_LOG_T(3)

πŸ’– SASL_LOG_T(3) β€” Cyrus SASL πŸ’–

okay bestie, so this one lives in the Cyrus SASL section of your man pages, and it's all about one lil callback that catches all the drama the SASL library wants to spill. no cap. 🫢


✨ NAME ✨

sasl_log_t β€” Cyrus SASL documentation πŸ““


🌸 SYNOPSIS 🌸

#include <sasl/sasl.h>

int sasl_log_t(void *context,
              int level,
              const char * message);

like… that's the whole vibe. three args, one job. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the function again, in all its glory, exactly as the library declares it:

int sasl_log_t(void *context,

int level,

const char * message);

and what does it do, you ask? sasl_log_t is the callback that logs all the warning/error messages coming out of the SASL library. it's giving "the group chat notification" of the SASL world β€” every little "hmm that didn't go great" gets routed through here. πŸ””

and if you don't specify one? syslog gets used instead. so the messages still go somewhere, they just go to the system's default spot. no biggie, but like… now you know. πŸ‘‘


πŸ’œ RETURN VALUE πŸ’œ

SASL callback functions should return SASL return codes β€” go peek at sasl.h for the complete list, it's all there. and SASL_OK means success, obviously. slay. βœ…


πŸ‘‘ SEE ALSO πŸ‘‘

like, go read those too. iykyk. πŸ“š


πŸŽ€ AUTHOR πŸŽ€

The Cyrus Team β€” iconic behavior fr fr. πŸ’–


1993-2016, The Cyrus Team


and that's a wrap on this one, bestie. this page came to you from Cyrus SASL version 2.1.28, dated February 18, 2022 β€” a whole lil moment in time, preserved forever. mwah. πŸ’‹βœ¨