7.3.4. Environment Variables which affect LN clients

LN_MANAGER

TCP/IP address of a listening ln-manager for the client to connect to. usually this will be automatically provided by the ln-manager in the default environment for each process. it is in the form of <HOST>:<PORT> where <HOST> can either be an IPv4-address in dotted-decimal notation or a domain-name that can be resolved by the local name resolver. PORT is the numeric listening TCP port of the manager to connect to.

this env-var is only used when a client is constructed via ln_init() or ln::client() and no manager address was explicitly provided either via function-arguments or the --ln-manager command-line parameter. (or when NULL is passed for the ln_manager-argument to ln_init_to_manager()).

LN_DEBUG

when set to 1 ln-clients will output internal debug messages to stdout.

For the corresponding ln_manager behavior under the same environment variable name, see the manager-side LN_DEBUG entry in Environment Variables which control the LNM.

LN_DEBUG_TO_FTRACE

when set to 1 ln-clients will output internal debug messages to /sys/kernel/debug/tracing/trace_marker independent of the setting of LN_DEBUG.

LN_FTRACE

when set to 1 ln-clients will output messages to /sys/kernel/debug/tracing/trace_marker before and after writing/reading to/from a topic shared memory.