Where Does runit Store Services?
runit keeps service dirs in /etc/sv and enables them by symlinking into /run/runit/service. Logs go to each service log folder.
Last updated
runit supervises whatever is linked into its service folder. Definitions live in /etc/sv, one folder per service with a run script inside. A symlink into the live service directory turns supervision on.
Void Linux symlinks /var/service to /run/runit/service, so guides mention both paths for the same place. If a service folder exists but sv reports failure, the link is usually missing rather than the definition.
Where runit stores this, by platform
/etc/sv
Service definitions. Each subfolder holds a run script and optional log/run. Never edited by the supervisor, safe to version.
/run/runit/service
Live supervision tree. Only symlinked services run. /var/service points here on Void and similar setups.
Frequently asked questions
How do I enable a runit service?
Symlink /etc/sv/name into /run/runit/service, or into /var/service where that convention is used. runit picks it up within seconds. Remove the link to stop supervision.
How do I check runit service status?
Run sv status name for state, sv restart name to bounce it. The sv tool talks to the supervise pipe inside the service folder, so it only works on enabled services.
Where are runit service logs?
Each supervised service with logging writes under its own log folder, commonly /var/log/name. There is no single journal to query.
Notice an outdated path? Let us know.