Where Does s6 Keep Services on Linux?
s6 supervision scandir, service directory layout and live state paths.
Last updated
s6 has no fixed distro layout. Upstream convention points the scanner at a service dir with live state under run. Distros like Artix add their own etc tree on top.
Service dirs follow a strict anatomy. Longrun versus oneshot markers, dependency folders and down flags decide behavior. Live copies symlink into the scandir rather than running in place.
Where s6 stores this, by platform
/run/service
Scanner and live state convention with distro overlays like Artix etc tree. Service dirs need run files plus type and dependency markers. Live copies symlink into the scandir. Repo and compiled DB paths vary.
Frequently asked questions
How do I back up s6 services?
No single folder covers it. Copy custom service dirs plus the repo and config roots with supervision stopped. Live symlinks and supervise fifos recreate at boot. Keep the compiled database backup beside the sources.
What goes inside a service directory?
Each service dir needs an executable run file. Type, dependencies and notification fds layer beside it. Optional log sub-services nest inside. Supervise and event dirs appear automatically at runtime.
Notice an outdated path? Let us know.