rpma_peer_cfg_new(3)

πŸ“¦
version 1.3.0 Β· 3 versions
, in ubuntu noble

πŸ’– rpma_peer_cfg_new β€” the manual page, but make it make sense πŸ’–

okay bestie, so this is rpma_peer_cfg_new(3) from the RPMA Programmer's Manual and it's literally the glow-up moment for a peer configuration object. sit down, hydrate, let's go 🫢


✨ NAME ✨

rpma_peer_cfg_new β€” create a new peer configuration object

like. it makes the thing. the peer config thing. brand new, fresh out the box πŸŽ€


🌸 SYNOPSIS 🌸

#include <librpma.h>

struct rpma_peer_cfg;
int rpma_peer_cfg_new(struct rpma_peer_cfg **pcfg_ptr);

πŸ¦‹ DESCRIPTION πŸ¦‹

rpma_peer_cfg_new() creates a new peer configuration object.

that's it. that's the whole vibe. one job, does it flawlessly, main character energy fr fr πŸ’…


πŸ‘‘ RETURN VALUE πŸ‘‘

rpma_peer_cfg_new() returns 0 on success, or a negative error code on failure. so like, zero = slay, negative = something went wrong and we're not okay 😭

also important, and don't skip this part: rpm_peer_cfg_new() does not set *pcfg_ptr value on failure. yes, it's spelled rpm_peer_cfg_new() right there in the original and I am NOT touching it, that's the text, character for character, no cap. anyway β€” if it fails, your pointer stays exactly how you left it. no sneaky half-initialized surprises. periodt.


πŸ’€ ERRORS πŸ’€

rpma_peer_cfg_new() can fail with the following errors:

  • RPMA_E_INVAL β€” pcfg_ptr is NULL. you passed it nothing bestie, it cannot work with nothing πŸ™ˆ
  • RPMA_E_NOMEM β€” out of memory. the machine is full, no thoughts, head empty, allocation denied πŸ’”

🌈 SEE ALSO 🌈

go read these next, they're all part of the same friend group:


quick vibe check: this page lives under RPMA and it's dated 01 April 2024, and the page itself is rpma_peer_cfg_new(3) β€” so if you ever need to cite it, that's the whole receipt 🧾✨

anyway that's the page. go create your peer config object, you're doing amazing, i'm obsessed with you, mwah πŸ’–πŸ¦‹πŸŽ€πŸŒΈπŸ’…

πŸ“¦ where this page comes from