rc_destroy(3)

πŸ“¦
version 1.5.2 Β· 4 versions
, in alpine 3.24, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ’… rc_destroy(3) β€” Radius client library, but make it a group chat

okay bestie, welcome to rc_destroy, a page from the Radius client library manual (section 3, the "library calls" section, iykyk). this one is short and sweet and honestly a little iconic for it. πŸŽ€


✨ NAME ✨

rc_destroy β€” and that's it, that's the whole name line. the description slot is literally empty in the original, so we're not gonna invent one. no cap, it just says the function name and then nothing. πŸ’€


🌸 SYNOPSIS 🌸

#include <radcli/radcli.h>

void rc_destroy(
    rc_handle  *rh
);

so you pull in <radcli/radcli.h> and then you call rc_destroy, you hand it one rc_handle *, and it gives you back nothing β€” that void return is giving "i don't owe you an explanation" energy and honestly? valid. ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

Destroys Radius Client handle reclaiming all memory.

that's the whole thing. it's the cleanup girlie. you built a handle, you did your Radius stuff, and now rc_destroy walks in, takes the handle, and reclaims all the memory that handle was holding onto. it's the "thanks for coming to my TED talk, everybody go home" of this library. πŸ§ΉπŸ’–

think of it as the closing bracket to rc_new(3). you opened the vibe, now you close the vibe. leaving handles lying around is not the move β€” that's a leak, and leaks are not slay. πŸ™ˆ

bestie PSA: once you've called this, the handle is gone gone. don't go poking at it afterwards, there is nothing left to poke. πŸ’€

πŸ‘‘ PARAMETERS πŸ‘‘

  • rh β€” the Radius client handle you want to free. that's the one. hand it over. 🫢

🌈 SEE ALSO 🌈

the whole friend group, alphabetically, every single one, no skipping:

radcli.h(3), rc_aaa(3), rc_aaa_ctx(3), rc_aaa_ctx_free(3), rc_aaa_ctx_get_secret(3), rc_aaa_ctx_get_vector(3), rc_aaa_ctx_server(3), rc_acct(3), rc_acct_proxy(3), rc_add_config(3), rc_apply_config(3), rc_auth(3), rc_auth_proxy(3), rc_avpair_add(3), rc_avpair_assign(3), rc_avpair_copy(3), rc_avpair_free(3), rc_avpair_gen(3), rc_avpair_get(3), rc_avpair_get_attr(3), rc_avpair_get_in6(3), rc_avpair_get_raw(3), rc_avpair_get_uint32(3), rc_avpair_insert(3), rc_avpair_log(3), rc_avpair_new(3), rc_avpair_next(3), rc_avpair_parse(3), rc_avpair_remove(3), rc_avpair_tostr(3), rc_buildreq(3), rc_check(3), rc_check_tls(3), rc_conf_int(3), rc_conf_srv(3), rc_conf_str(3), rc_config_free(3), rc_config_init(3), rc_destroy(3), rc_dict_addattr(3), rc_dict_addval(3), rc_dict_addvend(3), rc_dict_findattr(3), rc_dict_findval(3), rc_dict_findvend(3), rc_dict_free(3), rc_dict_getattr(3), rc_dict_getval(3), rc_dict_getvend(3), rc_find_server_addr(3), rc_get_socket_type(3), rc_get_srcaddr(3), rc_getport(3), rc_mksid(3), rc_new(3), rc_openlog(3), rc_own_hostname(3), rc_read_config(3), rc_read_dictionary(3), rc_read_dictionary_from_buffer(3), rc_send_server(3), rc_setdebug(3), rc_test_config(3), rc_tls_fd(3)

(yes, rc_destroy(3) is in its own SEE ALSO list. self-love, we respect it. πŸ’…)


and that's the page!! this manual came to you from radcli, dated 2023-01-29, and it lives at rc_destroy(3). free your handles, hydrate, and go read rc_new(3) next. periodt. πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from