radcli_ctx_..._dictionary(3)

💖 NAME 💖

radcli_ctx_read_dictionary — load an additional attribute dictionary, bestie. That’s the whole vibe. ✨

---

🌸 SYNOPSIS 🌸

#include <radcli/>

int radcli_ctx_read_dictionary(
    radcli_ctx  *ctx,
    const char  *path
);

---

🦋 DESCRIPTION 🦋

Okay so picture this: radcli_ctx_read_dictionary parses path — like, the actual ATTRIBUTE/VALUE/VENDOR lines using radcli’s dictionary grammar — straight into ctx’s dictionary. Obsessed. 💅

It is not needed for the common case, because radcli_ctx_read_config() already loads the file’s own dictionary= option. So don’t stress about it for the usual setup, fr fr.

Where it is useful? The programmatic ("backup") construction path, or when you wanna load more than one supplemental dictionary. Main character energy for extra dictionaries only. 👑

---

🎀 PARAMETERS 🎀

• ctx — a context from radcli_ctx_new() or radcli_ctx_read_config(). Gotta have your context, bestie.
• path — path to the dictionary file. Literally the file path. No cap.

---

⭐ RETURN VALUE ⭐

• 0 on success. Slay. ✅
• -1 on failure. And the failure cases are: an unreadable file, or a parse error — including a conflicting redefinition of an already-loaded attribute. Yeah, that last one is giving “we already have that at home” energy, and it is not a success. 😭

---

💜 SEE ALSO 💜

• radcli_ctx_apply(3)
• radcli_ctx_free(3)
• radcli_ctx_get_opt_int(3)
• radcli_ctx_get_opt_str(3)
• radcli_ctx_new(3)
• radcli_ctx_read_config(3)
• radcli_ctx_read_dictionary_from_buffer(3)
• radcli_ctx_set_opt_int(3)
• radcli_ctx_set_opt_str(3)
• radcli_ctx_set_secret(3)
• radcli_ctx_set_tls_psk(3)

---

mwah 💋 this radcli_ctx_..._dictionary(3) page is from the Radius client library, and the cute little footer situation says source/version radcli with date 2026-10-10. Byeee 🫶