Fork of Gerrit Pape's runit init/services management and execution framework.
  • C 91.7%
  • Shell 5.2%
  • CMake 3.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Frank Earl f418d24acf
Update to README.md.
We're going to let the people who're primary maintainers make decisions on their own.  No more committee.  No more code of conduct- just a statement of proper civilized conduct.  The other is flatly Woke...and has no business in this space.
2022-02-11 13:14:18 -06:00
doc Fix a sharp edge in documentation 2020-02-06 22:52:10 -06:00
include Added what I believe will let Dave's FreeBSD changes work 2017-07-25 08:15:02 -04:00
scripts Cleanups to scripting. 2017-07-24 23:58:12 -04:00
src Fix another config processor oops. 2020-02-06 22:58:28 -06:00
tests Cleanups to scripting. 2017-07-24 23:58:12 -04:00
.gitignore Additional .gitignore entries 2018-03-13 19:47:34 -04:00
CHANGES Missed updating the CHANGES file for 2.1.3 release. 2017-08-18 11:00:36 -04:00
CMakeLists.txt CMake: do not search for C++ compiler 2017-08-29 18:29:21 +02:00
ConfigureChecks.cmake properly put config.h for out-of-source builds 2017-08-17 18:52:57 +02:00
COPYING.md Update COPYING.md 2021-08-21 14:42:29 -05:00
README.md Update to README.md. 2022-02-11 13:14:18 -06:00
THANKS First go at re-working the documentation and scripting. 2017-07-13 22:57:14 -04:00
TODO First go at re-working the documentation and scripting. 2017-07-13 22:57:14 -04:00

runit

This is a fork of the runit init/services management framework originally developed by Gerrit Pape.

To quote the original website:

runit is a cross-platform Unix init scheme with service supervision, a replacement for sysvinit, and other init schemes. It runs on GNU/Linux, *BSD, MacOSX, Solaris, and can easily be adapted to other Unix operating systems."

It is the primary init solution for many Linux distributions, and the optional (and often preferred, even though optional) one for many more.

The purpose of this fork is several-fold:

  1. runit, while it works well enough for those distributions using it, hasn't had a real update in a while.
  2. While it builds well enough, it is not geared to readily package into many distributions- it is packaged as a slashpackage.
  3. While it builds well enough, it's build system is not geared for cross-compilation.
  4. There needs to be a relatively credible alternative to systemd, this is one of the same.
  5. While it is complete, and very capable, there are some aspects of fault tolerance not fully covered as well as they could be.

It is the intention of the long time Linux "Plumbers" that have undertaken this work to accomplish the above, providing a solid ecosystem around runit to provide what is believed to be a better answer to init/services management, that while it is differing from the sysv init structure that has gone before, is in keeping with the UNIX/*BSD/Linux philosophy of doing only init/services management, leaving other programs/schemes to handle udev, syslog, etc.