Artix user-installed service does not start automatically under runit or OpenRC
0 reputation · 27 Jul 2025, 15:27 UTC
Service does not activate automatically on Artix Linux
The goal is to diagnose why a user-installed service is not started automatically after installation on an Artix Linux system that uses runit or OpenRC as PID 1, without assuming a single default init system.
Enablement differs by init system: runit supervises services through symlinks under /etc/service to service directories under /etc/sv, while OpenRC manages enablement through runlevels with rc-update. Artix ISO and desktop editions ship different init systems by default, so the documented default and support priority are unclear until the running init system is confirmed.
Which init system does Artix treat as the default for service-enablement documentation? How can a user identify the correct enablement path for the init system running as PID 1? What is the recommended way to verify automatic activation without switching init systems?