NODEUPDOWN_IS_NODE_UP(3)
π NODEUPDOWN_IS_NODE_UP(3) π
okay bestie, welcome to the LIBNODEUPDOWN corner of the manual, section 3, and today's main character is nodeupdown_is_node_up π¦ (and its ride-or-die twin nodeupdown_is_node_down, we don't leave her out).
β¨ NAME β¨
nodeupdown_is_node_up, nodeupdown_is_node_down β test if a node is up or down
π SYNOPSIS π
#include <nodeupdown.h>
int nodeupdown_is_node_up(nodeupdown_t handle, const char *node); q.sp
int nodeupdown_is_node_down(nodeupdown_t handle, const char *node);
πΈ DESCRIPTION πΈ
nodeupdown_is_node_up() tests if the node pointed to by node is up. β¨
nodeupdown_is_node_down() tests if the node pointed to by node is down. π
the way that this one matters: the node name you pass into these functions must be the shortened name of the hostname. not the long one. the short one. periodt.
π₯ RETURN VALUES π₯
For nodeupdown_is_node_up(), 1 is returned if the node is up, 0 is returned if the node is down. For nodeupdown_is_node_down(), 1 is returned if the node is down, 0 is returned if the node is up. yes bestie, they're mirror images, it's giving opposites-attract π
On error, both return -1, and an error code is returned in handle. You can pull that error code with nodeupdown_errnum(3), and a description of it with nodeupdown_strerror(3). The error codes themselves live in nodeupdown.h.
π ERRORS π
NODEUPDOWN_ERR_NULLHANDLEβ thehandleparameter isNULL. girl. the nodeupdown handle must be created withnodeupdown_handle_create(3)first, no skipping steps πNODEUPDOWN_ERR_NOTLOADEDβnodeupdown_load_data(3)has not been called and no data has been retrieved. nothing's loaded, so there's nothing to check, we're just vibing in the void π«NODEUPDOWN_ERR_PARAMETERSβ an incorrect parameter has been passed in.NODEUPDOWN_ERR_OUTMEMβmalloc(3)has failed internally. πNODEUPDOWN_ERR_NOTFOUNDβ the node pointed to bynodeis not known. who is she? we don't know her πNODEUPDOWN_ERR_CLUSTERLIST_MODULEβ internal error with the clusterlist moduleNODEUPDOWN_ERR_HOSTLISTβ Hostlist API has failed internally.NODEUPDOWN_ERR_MAGICβhandlehas an incorrect magic number.handledoes not point to a nodeupdown handle, orhandlehas been destroyed bynodeupdown_handle_destroy(3). the magic is gone bestie, she's not who she said she was π
π FILES π
/usr/include/nodeupdown.h
π§ SEE ALSO π§
libnodeupdown(3), nodeupdown_handle_create(3), nodeupdown_load_data(3), nodeupdown_errnum(3), nodeupdown_strerror(3)
and that's the whole page, no cap π this one came to you from LLNL, back in August 2003, under the LIBNODEUPDOWN umbrella (yes the header says NODEUPDOWN_IS_NODE_UP(3) up top too, we see you). go forth and check your nodes, bestie πβ
π¦ where this page comes from
- epel 9: libnodeupdown-devel 1.14-41.el9 Β· GPLv2+
- fedora 43: libnodeupdown-devel 1.14-50.fc43 Β· GPL-2.0-or-later
- fedora 43: libnodeupdown-devel 1.14-50.fc43 Β· GPL-2.0-or-later
- fedora 44: libnodeupdown-devel 1.14-51.fc44 Β· GPL-2.0-or-later
- fedora 44: libnodeupdown-devel 1.14-51.fc44 Β· GPL-2.0-or-later
- Copyright (C) 2007-2011 Lawrence Livermore National Security, LLC
- Copyright (C) 2003-2007 The Regents of the University of California
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms