GEARMAN_CLIENT_CLONE(3)

🎀 NAME 🎀

gearman_client_clone — it's the Gearmand manual, bestie, and the whole scoop lives over at http://gearman.info/. This page is the section 3 one, aka GEARMAN_CLIENT_CLONE(3) 💅

---

✨ SYNOPSIS ✨

No cap, here's the whole vibe, verbatim:

#include <libgearman/gearman.h>

gearman_client_st <#c.gearman_client_st>
*gearman_client_create(gearman_client_st <#c.gearman_client_st> *client)

gearman_client_st <#c.gearman_client_st>
*gearman_client_clone(gearman_client_st <#c.gearman_client_st> *client,
const gearman_client_st <#c.gearman_client_st> *from)

void gearman_client_free(gearman_client_st <#c.gearman_client_st>
*client)

And you link with -lgearman, don't forget that part, it's giving essential 🫶

---

💖 DESCRIPTION 💖

Okay so first up, gearman_client_create() — it makes you a gearman_client_st struct, and that struct is literally the thing all the other libgearman client functions use to talk to the server. Main character energy fr. You've got two choices here: hand it a statically declared gearman_client_st, or hand it a NULL. And if you do pass in a NULL? Sweetie, it allocates a structure for you. Iconic. ✨

Then we've got gearman_client_clone(), which is like gearman_client_create()'s twin but with extra sauce — it copies the defaults and the list of servers from the source gearman_client_st. And if you pass a null as the argument for the source you're cloning from? That's literally the same as just calling gearman_client_create. If the destination argument is NULL, a gearman_client_st will be allocated for you too. So generous of it 💜

Now, cleanup time, because we're responsible queens 🌸. To free the memory tied to a gearman_client_st, pass it to gearman_client_free when you're done with it. And listen — gearman_client_free() is the only way to make sure all the memory is deallocated once you're finished with the structure. The only one. No shortcuts, no improvising 🙈

⚠️ Warning: you might wanna steer clear of using gearman_client_create() or gearman_client_clone() with a stack based allocation — and yes, we mean that first parameter. The most common issues related to ABI safety involve stack allocated structures. So like, don't do that. It's not the vibe. 💀

---

👑 RETURN VALUE 👑

• gearman_client_create hands back a pointer to the gearman_client_st that was created (or initialized). But if the allocation fails? It returns NULL. Sad but true 😭
• gearman_client_clone hands back a pointer to the gearman_client_st that was created (or initialized). And on an allocation failure? Also NULL. Same energy, same heartbreak.

---

🦋 HOME 🦋

Wanna know more? Go check out: http://gearman.info/ — she's got the lore ⭐

See also:

• gearmand(8)
• libgearman(3)
• gearman_strerror(3)
• gearman_client_st(3)

Author: Data Differential, http://www.datadifferential.com/ 💖

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

---

And that's a wrap, bestie 🫶 this was GEARMAN_CLIENT_CLONE(3) from the Gearmand manual, version 1.1.21+ds, dated Feb 04, 2026. Slay, go clone something responsibly 💅✨