NODEUPDOWN_ERRNUM(3)

πŸ“¦ version 1.14, in epel 9, fedora 43, fedora 44

πŸ’– NODEUPDOWN_ERRNUM πŸ’–

okay bestie, welcome to the nodeupdown error-handling corner of the LIBNODEUPDOWN manual, page NODEUPDOWN_ERRNUM(3). this is where you go when something went wrong and you need to find out what β€” no cap, it's giving detective energy πŸ”βœ¨


✨ NAME ✨

nodeupdown_errnum, nodeupdown_strerror, nodeupdown_errormsg, nodeupdown_perror β€” the nodeupdown error routines, aka the four little besties who tell you what broke 🫢


🌸 SYNOPSIS 🌸

#include <nodeupdown.h>

int nodeupdown_errnum(nodeupdown_t handle);

char *nodeupdown_strerror(int errnum);

char *nodeupdown_errormsg(nodeupdown_t handle);

void nodeupdown_perror(nodeupdown_t handle, const char *msg);

like, yes, that's the whole vibe. four functions, one header, zero drama πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

nodeupdown_errnum() πŸ’œ

returns the error code that's stored in handle. that's it, that's the whole job. she's simple, she's iconic, she serves.

nodeupdown_strerror() ✨

returns a pointer to a string that describes the error code errnum. so you hand her a number, she hands you words. glow-up moment fr fr.

generally, the whole flow is: you grab an error code with nodeupdown_errnum() and then you pass it straight to nodeupdown_strerror(). that's the pipeline, that's the routine, that's the group chat πŸ“²

nodeupdown_errormsg() πŸŽ€

returns a pointer to a string describing the error stored in handle. and like, logically speaking? she is literally equivalent to this:

char *nodeupdown_strerror(nodeupdown_errnum(nodeupdown_t handle));

not me just handing you the entire shortcut. you're welcome bestie 🫢

nodeupdown_perror() 🌈

this one is similar to perror(3) β€” same energy, different day. she produces a message on standard error output, describing the error stored in handle.

and here's the little detail that matters: if msg is not NULL, then the string pointed to by msg, a colon, and a blank are printed before the error message. so it's like msg: the actual error β€” cute little prefix, very main character ✨


πŸ“ FILES πŸ“

  • /usr/include/nodeupdown.h

that's where the header lives. go say hi 🧚


lowkey reminder: these are the routines you call when a nodeupdown_t handle is being mysterious and you need answers. always check the error, bestie. silence is not the vibe πŸ’€

sign-off time 🌸✨ this page came to you courtesy of LLNL, dated August 2003, from the LIBNODEUPDOWN manual, sitting pretty as NODEUPDOWN_ERRNUM(3). periodt. πŸ’…πŸ‘‘

πŸ“¦ where this page comes from