QB_LOOP_SIGNAL_MOD(3)

πŸ’… qb_loop_signal_mod β€” the libqb programmer's manual glow-up

okay bestie, so this one is qb_loop_signal_mod(3) from the libqb Programmer's Manual, and it's literally the glow-up artist for your signal jobs ✨


🌸 NAME 🌸

qb_loop_signal_mod β€” Modify the signal job.

like… you already have a signal job, and now you're giving it a lil makeover πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

#include <qb/qbloop.h>

int32_t qb_loop_signal_mod(
    qb_loop_t                  *l,            /* pointer to the loop instance */
    enum qb_loop_priority       p,            /* the priority */
    int32_t                     sig,          /* (SIGHUP or SIGINT) etc .... */
    void                       *data,         /* user data passed into the dispatch function */
    qb_loop_signal_dispatch_fn  dispatch_fn,  /* callback function */
    qb_loop_signal_handle       handle        /* (in) a reference to the signal job */
);

she takes six whole arguments and she's not sorry about it 🫢


πŸ¦‹ PARAMS πŸ¦‹

  • l β€” pointer to the loop instance. that's your main character loop, the one running the whole show πŸ‘‘
  • p β€” the priority. pick your vibe tier, more on that below ⬇️
  • sig β€” (SIGHUP or SIGINT) etc .... yes, the manpage literally says "etc ...." and honestly? valid 🌈
  • data β€” user data passed into the dispatch function. your lil care package, hand-delivered πŸ“¦
  • dispatch_fn β€” callback function. the one who actually gets called when it's time to do the thing πŸ“ž
  • handle β€” (in) a reference to the signal job. this is the one you're modifying, so it's in, not out πŸ’–

✨ DESCRIPTION ✨

bestie… the original page has the DESCRIPTION heading and then literally nothing under it. no cap. zero words. an empty section. the silence is deafening 😭

so like, i'm not gonna invent lore for you β€” the real info is all up in the synopsis and params, and that's what we're working with πŸ’€


🌈 STRUCTURES 🌈

here's the priority enum, exactly as she is:

enum qb_loop_priority {
      QB_LOOP_LOW;
      QB_LOOP_MED;
      QB_LOOP_HIGH;
};

low, med, high. a whole three-tier system and every single one of them ate πŸ’…


⭐ RETURN VALUE ⭐

status (0 == ok, -errno == failure)

so if you get 0? slay, we're so back πŸŽ‰ if you get -errno? that's a fail, and the errno tells you why, so go read it, iykyk πŸ™ˆ


πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, no one left behind:


Copyright (C) 2010-2020 Red Hat, Inc.


fr fr: everything above is exactly what the page says β€” i just gave it the energy it deserved πŸ’œ

okay that's the whole page, ily, go modify your signal job responsibly 🧚 and yes, this was libqb, dated 2025-09-16, manual page QB_LOOP_SIGNAL_MOD(3) β€” periodt πŸ’…βœ¨

πŸ“¦ where this page comes from