Installer runit avec Homebrew, apk, apt, MacPorts, Nix

Liens du projet

• Page d'accueil
• Page du gestionnaire de paquets

Commandes et alias

• chpst
• runit
• runit-init
• runsv
• runsvchdir
• runsvdir
• svlogd
• utmpset

Historique du projet

Gerrit Pape developed runit as a cross-platform Unix init scheme and service-supervision suite. Early public documentation and source identifiers date from 2002, when it was already being used as PID 1 on Debian systems.

The design divides boot, normal operation, and shutdown into three scripts. During normal operation, `runsvdir` supervises service directories, restarts failed services, and integrates with runit's logging tools.

Successive releases refined supervision, service-control compatibility, logging, portability, process reaping, runlevels, and filesystem-layout guidance while preserving the core architecture.

Historique d'adoption

The official site lists runit packages or integrations for Debian, Ubuntu, FreeBSD, OpenBSD, NetBSD, Gentoo, Arch Linux, Linux From Scratch, Artix, antiX, and other systems. It is especially notable as the default init scheme of Void Linux and an alternative init on several other distributions.

The project also documents use on GNU/Linux, BSD systems, macOS, Solaris, and operation either as PID 1 or alongside a traditional init system.

Modes d'utilisation

As PID 1, runit executes `/etc/runit/1` for one-time initialization, keeps `/etc/runit/2` running during normal operation, and executes `/etc/runit/3` for shutdown or reboot. Administrators normally place per-service run scripts in service directories managed by `runsvdir`, inspect or change state with `sv`, and handle logs with `svlogd`.

Pourquoi les passionnés de paquets s'y intéressent

runit is a touchstone in Unix service-supervision culture because it combines a small three-stage init design with persistent per-service supervision and straightforward run scripts. It offers a contrasting model to SysV init scripts and larger dependency-oriented service managers.

Its tiny tools—such as `runsv`, `runsvdir`, `sv`, `svlogd`, and `chpst`—are independently useful and embody the Unix preference for narrowly scoped components.

Chronologie

• 2002: Contemporary source identifiers and the official usage example document runit operating as PID 1.
• 2004: Official documentation covered runlevels and service-dependency practices.
• Later 1.x releases expanded logging, service control, portability, and process-reaping behavior.
• The 2.x series refined defaults, shutdown behavior, service checks, and configuration guidance.

Related projects

• runit belongs to the daemontools-derived supervision family and can replace SysV-style init or operate alongside an existing init system. Its supervision model also influenced later lightweight init and service-management ecosystems.

Sources

• Official installation documentation: https://smarden.org/runit/install
• Official project site: https://smarden.org/runit/
• Official source repository linked by the project site: https://github.com/g-pape/runit
• Official upgrade history: https://smarden.org/runit/upgrade