NOZZLE_RUN_UPDOWN(3)

✨ NOZZLE_RUN_UPDOWN ✨

okay bestie so this is nozzle_run_updown(3) from the Kronosnet Programmer's Manual and it's literally the glow-up your nozzle device deserves πŸ’…


πŸ’– NAME πŸ’–

nozzle_run_updown β€” run the updown commands that are associated with a nozzle device πŸŽ€


🌸 SYNOPSIS 🌸

#include <libnozzle.h>

int nozzle_run_updown(
    const nozzle_t  nozzle,
    uint8_t         action,
    char          **exec_string
);

πŸ¦‹ DESCRIPTION πŸ¦‹

so nozzle_run_updown is the moment okay, here's the whole vibe:

  • nozzle β€” pointer to the nozzle struct 🫢
  • action β€” pre-up.d / up.d / down.d / post-down.d (peep the defines above, they're right there πŸ‘€)
  • exec_string β€” pointers to string to record executing action stdout/stderr. The string is malloc'ed, so the caller needs to free the buffer. If the script generates no output this string might be NULL. πŸ™ˆ

and like, it is the application responsibility to call helper scripts before or after creating/destroying interfaces or IP addresses. that's on you, not on the library, no cap πŸ‘‘


⭐ RETURN VALUE ⭐

  • 0 on success 😌
  • -1 on error and errno is set (sanity checks and internal calls. β€” yes, that sentence is doing its own thing, we're keeping it fr fr)
  • -2 on error from executing the shell scripts, and no errno is set. the shell scripts said no πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

your reading list, bestie, go off πŸ“š


Copyright (C) 2010-2026 Red Hat, Inc. All rights reserved. 🫑


and that's the whole page babes β€” this is from kronosnet, dated 2026-07-20, and the manual is NOZZLE_RUN_UPDOWN(3) πŸ’œ stay hydrated, free your malloc'ed strings, mwah πŸŽ€βœ¨

πŸ“¦ where this page comes from