GEARMAN_CLIENT_SET_WARNING_FN(3)

✨ NAME ✨

gearman_client_set_warning_fn — it's giving Gearmand Documentation energy, bestie 💖 and the docs live at http://gearman.info/ if you wanna go touch grass over there.

---

🌸 SYNOPSIS 🌸

okay so first things first, you gotta pull in the header:

#include <libgearman/gearman.h>

and then these types??? iconic, we love them all:

• type gearman_actions_t
• type gearman_workload_fn
• type gearman_created_fn
• type gearman_data_fn
• type gearman_warning_fn
• type gearman_universal_status_fn
• type gearman_exception_fn
• type gearman_fail_fn
• type gearman_complete_fn

and the functions themselves, right, they all look like this:

void gearman_client_set_workload_fn(gearman_client_st *client, gearman_workload_fn *function)

void gearman_client_set_created_fn(gearman_client_st *client, gearman_created_fn *function)

void gearman_client_set_data_fn(gearman_client_st *client, gearman_data_fn *function)

void gearman_client_set_warning_fn(gearman_client_st *client, gearman_warning_fn *function)

void gearman_client_set_status_fn(gearman_client_st *client, gearman_universal_status_fn *function)

void gearman_client_set_complete_fn(gearman_client_st *client, gearman_complete_fn *function)

void gearman_client_set_exception_fn(gearman_client_st *client, gearman_exception_fn *function)

void gearman_client_set_fail_fn(gearman_client_st *client, gearman_fail_fn *function)

void gearman_client_clear_fn(gearman_client_st *client)

const char *gearman_client_do_job_handle(gearman_client_st *client)

and last but never least: you gotta link against -lgearman or nothing works, fr fr 🫶

---

💅 DESCRIPTION 💅

so basically?? these are the callbacks for client execution task states. the whole vibe. ✨

• gearman_client_set_data_fn() — sets the callback function that gets called if the server is gonna make a request to the client asking for more data. the server is like "bestie give me more" and your callback handles it 💌
• gearman_client_do_job_handle() — gets the job handle for the running task. lowkey the important part: this should be used between repeated gearman_client_do() (and related) calls to get information. so like, in the gap between them, not randomly mid-call, okay?? 😤
• gearman_client_clear_fn() — you can call this to remove all existing gearman_actions_t that have been set. full reset, clean slate, era ended 🧹✨

okay and now the big group: gearman_client_set_created_fn(), gearman_client_set_data_fn(), gearman_client_set_warning_fn(), gearman_client_set_status_fn(), gearman_client_set_complete_fn(), gearman_client_set_exception_fn(), and gearman_client_set_fail_fn() — these all set callback functions for the different states of execution for a client request. and here's the tea ☕: each request, ie a creation of gearman_task_st, keeps a copy of the callbacks when it is created. a copy!! so it's not vibing off your live changes later, she took a screenshot and moved on 📸

also important queen: gearman_client_set_exception_fn() will ONLY be called if exceptions are enabled on the server. you turn those on by calling gearman_client_set_server_option().

here's what that looks like in practice, no cap:

const char *EXCEPTIONS="exceptions";
gearman_client_set_server_option(client, EXCEPTIONS, strlen(EXCEPTIONS));

like. look at her go. 💅

---

🎀 RETURN VALUE 🎀

None — nothing, zero, nada, she returns the void and the void is fine 🫧

See also:

• gearmand(8)
• libgearman(3)
• gearman_client_error(3)
• or gearman_worker_error(3)

---

👑 Author 👑

Data Differential http://www.datadifferential.com/ — the icons themselves 💜

🌈 Copyright 🌈

2011-2014, Data Differential, http://www.datadifferential.com/ — respect the elders, protect the legacy 🥹

---

and that's the whole page babes, we did it 💖 this was pulled from the 1.1.21+ds era of the Gearmand manual, dated Feb 04, 2026, and it's officially titled GEARMAN_CLIENT_SET_WARNING_FN(3). go forth and set those callbacks, bestie 🦋✨