Where Does SvxLink Store Its Config?
SvxLink reads ~/.svxlink/svxlink.conf first, then /etc/svxlink/svxlink.conf, with module drop-ins and a --config override.
Last updated
SvxLink hunts config user-first: ~/.svxlink/svxlink.conf wins when present, otherwise /etc/svxlink/svxlink.conf, with --config forcing any path. Module fragments in svxlink.d/ append per-module sections.
Reflector keys live apart in /var/lib/svxlink/pki and deserve backup priority over everything else. Config mistakes break audio; key loss breaks identity.
Where SvxLink stores this, by platform
/etc/svxlink/svxlink.conf
Logics, modules, events, reflector keys path. --config beats the whole chain; hidden and non-.conf files in svxlink.d are ignored.
Frequently asked questions
Where do repeater module configs go?
Put per-module files in /etc/svxlink/svxlink.d/. Every *.conf there loads as extra config, which keeps the main file readable as node complexity grows.
What must I never lose as a SvxReflector node?
Back up /var/lib/svxlink/pki/MYCALL.key immediately. Losing it locks you out of the reflector; anyone holding a copy can log in as your node.
Notice an outdated path? Let us know.