GEARMAN_CLIENT_SET_WORKLOAD_MALLOC_FN(3)

✨ NAME ✨

gearman_client_set_workload_malloc_fn — Gearmand Documentation, <http://gearman.info/>

okay bestie so this is the gearman_client_set_workload_malloc_fn(3) page from the libgearman manual, and it's lowkey a whole little bundle of client functions, not just the one malloc thing. stay with me, it all makes sense I promise 💖

---

🫶 SYNOPSIS 🫶

#include <libgearman/gearman.h>

type gearman_client_st

type gearman_task_context_free_fn

int gearman_client_timeout(gearman_client_st *client)

void gearman_client_set_timeout(gearman_client_st *client, int timeout)

void *gearman_client_context(const gearman_client_st *client)

void gearman_client_set_context(gearman_client_st *client, void *context)

void gearman_client_set_workload_malloc_fn(gearman_client_st *client,
gearman_malloc_fn *function, void *context)

void gearman_client_set_workload_free_fn(gearman_client_st *client,
gearman_free_fn *function, void *context)

void gearman_client_task_free_all(gearman_client_st *client)

void gearman_client_set_task_context_free_fn(gearman_client_st *client,
gearman_task_context_free_fn *function)

⚠️ heads up: gearman_client_set_workload_malloc_fn() and gearman_client_set_workload_free_fn() are Deprecated since version 0.23. Use gearman_allocator_t instead, bestie, it's the glow-up version. 💅

and one more thing: link with -lgearman. do not forget her, she's the whole point. 🔥

---

🌸 DESCRIPTION 🌸

gearman_client_st is used for client communication with the server. that's her whole job, and she's iconic at it. 👑

gearman_client_context() and gearman_client_set_context() can be used to store an arbitrary object for the user. yes literally arbitrary. a pointer to your little guys. your stuff. anything. ✨

gearman_client_set_task_context_free_fn() sets a trigger that will be called when a gearman_task_st is released. think of it as a goodbye callback, it's giving closure energy. 🦋

gearman_client_timeout() and gearman_client_set_timeout() get and set the current connection timeout value, in milliseconds, for the client. so, y'know, how long she waits before she's like "okay this is not happening". ⏳

normally malloc(3) and free(3) are used for allocation and releasing workloads. gearman_client_set_workload_malloc_fn() and gearman_client_set_workload_free_fn() can be used to replace these with custom functions. (these have been deprecated, please see gearman_allocator_t for the updated interface.) ⭐

gearman_client_task_free_all() is used to free all current gearman_task_st that have been created with the gearman_client_st. she clears the whole roster, no survivors, main character cleanup. 🧹

Warning: by calling gearman_client_task_free_all() you can end up with a SEGFAULT 💀 if you try to use any gearman_task_st that you have kept pointers too. so like. if you kept a pointer. and you use it after. that's a crash. that's on you bestie, the manpage told you fr fr.

---

🎀 RETURN VALUE 🎀

gearman_client_timeout() returns an integer representing the amount of time in milliseconds to wait for a connection before throwing an error.

a value of -1 means an infinite timeout value. she will wait. forever. periodt. 💜

---

🌈 HOME 🌈

to find out more information please check: <http://gearman.info/>

See also:

• gearmand(8)
• libgearman(3)
• gearman_client_create(3)

---

👑 Author 👑

Data Differential <http://www.datadifferential.com/>

🍓 Copyright 🍓

2011-2014, Data Differential, <http://www.datadifferential.com/>

---

and that's the whole page angel, version 1.1.21+ds, dated Feb 04, 20 (the footer got clipped, we don't make the rules 🙈). go forth and set your workload malloc fn, or better yet, use gearman_allocator_t like a modern queen. slay, hydrate, and read your manpages. 💖✨🫶