Where Does InspIRCd Store Config and Data?
InspIRCd splits config, data and logs across FHS paths on Linux packages, unlike UnrealIRCd's single tree. Includes and paths resolve relatively.
Last updated
InspIRCd follows distro filesystem law. Config anchors /etc with includes for modules, operators and messages. Data and runtime land in lib trees while logs take the log tree with filename variants by distro.
Source builds mirror the shape under a run prefix instead. Relative paths resolve against config with overrides for every tree. UnrealIRCd inverts the model with one self-contained directory, making the contrast worth stating.
Where InspIRCd stores this, by platform
/etc/inspircd/inspircd.conf
Mandatory XML config with modules, opers and motd includes beside it. Relative resolution against config dir with per-tree overrides. Examples ship alongside for reference.
/var/lib/inspircd
Package data and runtime trees with PID placement varying by distro. UnrealIRCd keeps equivalents inside one install tree instead. Check config for custom overrides.
/var/log/inspircd
Log directory with filename variants by distro and target settings. Debian single-file forms differ from directory forms. Custom destinations configure through log targets.
Frequently asked questions
How do I back up InspIRCd config?
Copy /etc/inspircd with its main XML plus modules, opers and motd includes. Relative paths resolve against the config dir with overrides available. Example configs ship beside the live ones for reference.
How does InspIRCd differ from UnrealIRCd?
They invert each other. InspIRCd packages split etc, lib and log trees while UnrealIRCd keeps conf, data and logs in one install tree. Syntax differs too, with XML includes versus quoted remote-capable includes.
Notice an outdated path? Let us know.