radcli_ctx_read_config(3)

πŸ“¦ version 2.0.1, in arch rolling

🌸 NAME

Okay so this is radcli_ctx_read_config(3), from the Radius client library manual, and it's the create-a-context-by-parsing-a-config-file function. Fr fr it's the main, recommended way to configure radcli. πŸ’–


✨ SYNOPSIS

#include <radcli/>

radcli_ctx * radcli_ctx_read_config(
    const char  *filename,
    unsigned     flags
);

πŸ’… DESCRIPTION

It parses filename, validates every single option, initialises the transport β€” including the TLS/DTLS handshake for TLS/DTLS transports, no cap β€” and loads the built-in RFC 2865/2866/2869 dictionary plus the file's own dictionary= option, if set. That means radcli_ctx_read_dictionary() need not be called separately for the common case, unless RADCLI_CTX_NO_BUILTIN_DICT is set in flags. ✨

It uses the same file format and recognised options as radcli.h's rc_read_config(), so an existing radiusclient.conf written for the legacy API loads unchanged. Iconic behavior, honestly. πŸ¦‹


πŸŽ€ PARAMETERS

  • filename β€” path to the configuration file. Simple as that. πŸ“
  • flags β€” a bitwise OR of radcli_ctx_flags, or 0 for the common case. Slay. πŸ‘‘

🫢 RETURN VALUE

Returns the new context, or NULL on failure (missing/unreadable file, invalid option, an unknown flags bit, or transport initialisation failure). Like, if something's off, you get NULL, not a vibe. 😭


πŸ‘€ SEE ALSO


That's the whole page, bestie. This absolute icon ships with radcli, dated 2026-10-10, and its page is radcli_ctx_read_config(3). Periodt. πŸ’œ

πŸ“¦ where this page comes from