From e4821d7a10ee2096b689a66baa9b974d51339bc3 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Tue, 23 May 2017 11:05:54 +0000 Subject: Switch doc to schemeless URLs --- doc/why.html | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'doc/why.html') diff --git a/doc/why.html b/doc/why.html index 775f81d..157a27e 100644 --- a/doc/why.html +++ b/doc/why.html @@ -6,14 +6,14 @@ s6-rc: why? - +

s6-rc
-Software
-skarnet.org +Software
+skarnet.org

Why s6-rc ?

@@ -22,7 +22,7 @@

Supervision suites such as -s6, +s6, runit, perp or daemontools @@ -32,7 +32,7 @@ way in a controlled environment and keep it alive if it dies; they also provide daemon management tools to, among others, send signals to the daemon without knowing its PID. They can control individual long-lived processes perfectly well, and -s6 also provides +s6 also provides tools to manage a whole supervision tree. To any system administrator concerned about reliability, supervision suites are a good thing.

@@ -132,7 +132,7 @@ oneshots or longruns, one by one, even when the dependency graph says that some services could be started in parallel. Also, the daemons they start are always unsupervised, even when the underlying init system provides supervision features. There usually is no -readiness +readiness notification support on daemons either, daemons are fire-and-forget (but that's more on the scripts themselves than on the frameworks). Another common criticism @@ -195,7 +195,7 @@ guys.
  • systemd, the main protagonist (or antagonist) in the "init wars". It has the same problems as launchd, up by an order of magnitude; -here is why. +here is why. systemd avowedly aims to replace the whole low-level user-space of Linux systems, but its design is horrendous. It doesn't even get readiness notification right.
    • @@ -246,16 +246,16 @@ readiness notification support, reproducible script execution, and sysv-rc or OpenRC. It is not an init system. You can run s6-rc with any init system of your choosing. Of course, s6-rc requires a -s6 supervision tree to be running on +s6 supervision tree to be running on the system, since it delegates the management of longrun services to that supervision tree, but it does not require that s6 be the init system itself. s6-rc will work -when s6-svscan +when s6-svscan runs as process 1 (on Linux, such a setup can be easily achieved via the help of the -s6-linux-init +s6-linux-init package), and it will also work -when +when s6-svscan runs under another init process.
  • The service manager runs on top of a supervision suite. It does not try to make it perform boot/shutdown operations or @@ -277,7 +277,7 @@ simple, in order to allow external tools to automatically write service definitions for s6-rc - for instance for conversions between service manager formats.
  • Like every -skarnet.org tool, s6-rc +skarnet.org tool, s6-rc is made of very little code, that does its job and nothing else. The binaries are small, it is very light in memory usage, and the code paths are extremely short.
    • -- cgit v1.2.3