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:
qb_loop_job_del(3)qb_loop_run(3)qb_loop_create(3)qb_loop_stop(3)qb_loop_poll_low_fds_event_set(3)qb_loop_signal_del(3)qb_loop_signal_add(3)qb_loop_job_add(3)qb_loop_poll_del(3)qb_loop_destroy(3)qb_loop_timer_expire_time_remaining(3)qb_loop_poll_mod(3)qb_loop_timer_del(3)qb_loop_timer_add(3)qb_loop_timer_is_running(3)qb_loop_timer_expire_time_get(3)qb_loop_poll_add(3)
π COPYRIGHT π
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
- fedora 44: libqb-devel 2.0.9-2.fc44 Β· LGPL-2.1-or-later
- fedora 44: libqb-devel 2.0.9-2.fc44 Β· LGPL-2.1-or-later
- ubuntu resolute: libqb-dev 2.0.9-1ubuntu1 Β· LGPL-2.1-or-later
- ubuntu stonking: libqb-dev 2.0.9-1ubuntu1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms