runit
Original author(s)Gerrit Pape
Initial releaseFebruary 10, 2004 (2004-02-10)[1]
Stable release
2.1.2 / August 10, 2014 (2014-08-10)[2]
Written inC, Shell
Operating systemLinux, FreeBSD, OpenBSD, NetBSD, macOS, Solaris
TypeInit daemon
LicenseNew BSD License
Websitesmarden.org/runit/ Edit this on Wikidata

runit is an init and service management scheme for Unix-like operating systems that initializes, supervises, and ends processes throughout the operating system. Runit is a reimplementation of the daemontools[3] process supervision toolkit that runs on many Linux-based operating systems, as well as BSD, and Solaris operating systems. Runit features parallelization of the start up of system services, which can speed up the boot time of the operating system.[4]

When running as an init daemon, Runit is the direct or indirect ancestor of all other processes. It is the first process started during booting, and continues running until the system is shut down. It is often used with other init systems as a separate service manager. In the service manager role, it can be used by unprivileged users to orchestrate personal services, as well as by root to manage services not otherwise managed by the init system currently in use.

Runit booting Void Linux

Design

Runit focuses on being a small, modular, and portable codebase. In the init role, Runit is split into three stages: one time initialization, process supervision, and halting or rebooting. While the first and third stages must be adapted to the specific operating system they are running on, the second stage is portable across all POSIX compliant operating systems.[5] The 3 stages can be configured through 3 executable files (they are usually shell scripts) named, respectively, 1, 2, and 3.

Stage 2 usually invokes a binary named runsvdir, which is the process responsible for global daemon management: for every daemon it finds in a folder passed to it by argument, it then spawns an individual watchdog, each of those starts a daemon (and a logger service eventually associated to it) and restarts it if it dies. In case a daemon is added or removed, it kills the watchdog or starts a new one. Executable files with specific names are used to describe the various phases of the daemon's life (run, check, finish, ...), it can intercept signals sent and run by specific scripts if they exist, and named pipes are created to expose interfaces to control the daemon.

Usage

Runit can be used either as a drop-in replacement[6] for sysvinit, or as a service supervisor (with sysvinit as the parent PID 1 process which runs processes specified by the inittab file, or some other init system).[7] The RubyWorks stack of software able to run Ruby on Rails incorporated Runit into its suite.[8]

Adoption

Runit is the default init system of:

Runit is an "officially" available init system for:

References

  1. ↑ Pape, Gerrit (2004-02-10). "runit-1.0.0 release". gmane.comp.sysutils.supervision.general (Mailing list). Archived from the original on 2013-12-13. Retrieved 2013-12-10.
  2. ↑ Pape, Gerrit (2009-10-04). "runit - installation". smarden.org. Retrieved 2014-08-10.
  3. ↑ Purcell, Steve (2007-11-11). "Init Scripts Considered Harmful". sanityinc.com. Retrieved 12 December 2013.
  4. ↑ Pape, Gerrit. "runit - benefits". Retrieved 23 April 2013.
  5. ↑ Pape, Gerrit. "runit - benefits". Retrieved 23 April 2013.
  6. ↑ Pape, Gerrit. "replacing init". Retrieved 11 August 2014.
  7. ↑ Pape, Gerrit. "use with traditional init". Retrieved 11 August 2014.
  8. ↑ "Process management with runit". rubyworks.rubyforge.org. Retrieved 14 April 2014.
  9. ↑ "VoidLinux". Retrieved 28 June 2020.
  10. ↑ "Gentoo". Retrieved 8 September 2023.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.