Hi! Advanced apologies for the synthesized inquiry, I think I can script this up but I'm interested in any community solutions and LLM seems to have expanded my inquiry correctly:
Would anyone here be willing to share how they integrate **runit** under a `systemd`-managed environment, specifically on RHEL 8, using `systemctl` as the primary interface? The goal on this site is to demonstrate daemontools‑style services in a way that is familiar and low‑risk for existing RHEL 8 administrators. In particular, I’m interested in running `runsvdir` under `systemd` (as a normal unit), so that I can showcase an alternate service tree and supervision model in its own prefix, without replacing PID 1 or taking over any existing units. Administrators would continue to use their normal `systemctl` workflows, while I provide an isolated set of `run` scripts and environment directories for evaluation. If there is a well‑known or broadly used pattern for this (unit template, directory layout, enable/disable conventions, logging approach, etc.), I would prefer to adopt something recognizable to the community rather than invent yet another scheme. Pointers to existing configurations, repositories, or “this is what we deploy in production” examples would be especially appreciated. Best regards, - George Would anyone here like to share their implementation of runit under systemctl? The idea is to demonstrate daemontools style services at a RHEL8 site. The runsvdir value add conversation is much simpler as systemd unit, where I can demonstrate services structure without needing to introduce new commands to keep administrators in control. systemctl daemon-reload systemctl enable --now runit.service On Sun, Nov 9, 2025 at 11:12 AM G. Pape <[email protected]> wrote: > Hi, version 2.3.0 of the runit package is available through > > https://smarden.org/runit/ > -- George Georgalis, (415) 894-2710, http://www.galis.org/
