NODEUPDOWN_GE..._NODES_STRING(3)

💖 NODEUPDOWN_GET_UP_NODES_STRING 💖

okay so bestie, welcome to the nodeupdown girlies' corner of LIBNODEUPDOWN 💅 this is the man page for nodeupdown_get_up_nodes_string and its ride-or-die twin nodeupdown_get_down_nodes_string, and no cap, they're about to hand you a whole ranged string of nodes like it's nothing. periodt.

---

✨ NAME ✨

nodeupdown_get_up_nodes_string, nodeupdown_get_down_nodes_string — get up or down nodes 🦋

---

🌸 SYNOPSIS 🌸

#include <nodeupdown.h>

int nodeupdown_get_up_nodes_string(nodeupdown_t handle, char *buf, int
buflen);

int nodeupdown_get_down_nodes_string(nodeupdown_t handle, char *buf, int
buflen);

---

💜 DESCRIPTION 💜

so nodeupdown_get_up_nodes_string() goes and fetches a ranged string of nodes that are up and drops it right into the buffer that buf is pointing at. iconic behaviour honestly.

and buflen? that's you telling it how long your buffer is. pls don't lie to it, it will not recover. 🙈

then nodeupdown_get_down_nodes_string() is literally the exact same function, same energy, same everything — except it retrieves a ranged string of down nodes. that's it. that's the whole difference. slay.

---

🎀 RETURN VALUES 🎀

• On success? it returns 0 ✨ we love a clean win.
• On error? it returns -1 😭 and an error code gets handed back in handle.

you can grab that error code with nodeupdown_errnum(3), and get a whole description of it with nodeupdown_strerror(3). the error codes themselves are chillin' over in nodeupdown.h.

---

💀 ERRORS 💀

like, here's the whole drama list, bestie:

• NODEUPDOWN_ERR_NULLHANDLE — the handle parameter is NULL. literally nothing there. the nodeupdown handle has to be created with nodeupdown_handle_create(3) first, okay? 🫶
• NODEUPDOWN_ERR_NOTLOADED — nodeupdown_load_data(3) has not been called and no data has been retrieved. it's giving empty. it's giving nothing to work with.
• NODEUPDOWN_ERR_PARAMETERS — an incorrect parameter has been passed in. 🙈 something you gave it was just... not it.
• NODEUPDOWN_ERR_OVERFLOW — the buffer pointed to by buf is not large enough to store the ranged string of nodes. it simply does not fit and it is NOT gonna pretend otherwise.
• NODEUPDOWN_ERR_OUTMEM — malloc(3) has failed internally. memory said no. 💀
• NODEUPDOWN_ERR_CLUSTERLIST_MODULE — internal error with the clusterlist module. not your fault, not our fault, it's just an internal moment.
• NODEUPDOWN_ERR_HOSTLIST — Hostlist API has failed internally. same vibe, different module.
• NODEUPDOWN_ERR_MAGIC — handle has an incorrect magic number 🔮 handle does not point to a nodeupdown handle, or handle has been destroyed by nodeupdown_handle_destroy(3). so either it was never a real handle or you already killed it. either way, it's gone, girl.

---

🍓 FILES 🍓

• /usr/include/nodeupdown.h

---

🌈 SEE ALSO 🌈

libnodeupdown(3), nodeupdown_handle_create(3), nodeupdown_load_data(3), nodeupdown_get_up_nodes_list (3), nodeupdown_get_down_nodes_list (3), nodeupdown_errnum(3), nodeupdown_strerror(3)

---

ngl if you're still confused, go read the _list versions instead — sometimes you just want the list, not the ranged string. iykyk 😌

---

k bye bestie, this one came from LLNL, dated August 2003 — yeah she's vintage but she still ate 💅👑 mwah 🫶