From e4821d7a10ee2096b689a66baa9b974d51339bc3 Mon Sep 17 00:00:00 2001
From: Laurent Bercot
s6-rc
-Software
-skarnet.org
+Software
+skarnet.org
s6-rc: Frequently Asked Questions
@@ -93,7 +93,7 @@ file.
Using the filesystem as a key-value store is
a good technique to avoid parsing, and skarnet.org packages do it
everywhere: for instance,
-s6-envdir
+s6-envdir
uses the file name as a key and the file contents as a value.
The s6-rc-compile source format is just another instance of this
technique.
@@ -196,7 +196,7 @@ time you compile a service database, you could run:
stamp=`s6-clock`
@@ -218,14 +218,14 @@ new database will be used on the next boot, atomically update the link:
s6-ln -nsf compiled-$stamp /etc/s6-rc/compiled
The use of the
-s6-ln
+s6-ln
utility is recommended, because the
ln
standard actually forbids an atomic replacement, so utilities that
follow it to the letter, for instance, ln from GNU coreutils, cannot
be atomic: they first remove the old link, then create the new one. If you
do not have
-s6-ln,
+s6-ln,
you need to perform an unintuitive workaround to get POSIX-compliant tools to
do the right thing:
ln -sf compiled-$stamp /etc/s6-rc/compiled/compiled &&
@@ -284,7 +284,7 @@ using OpenRC
In your boot script (/etc/rc.init, for instance, if you're using -s6-linux-init), +s6-linux-init), after invoking s6-rc-init, just ask s6-rc to start the set of services you want up @@ -416,7 +416,7 @@ addressed by Unix distributions.
- Like the rest of skarnet.org + Like the rest of skarnet.org software, s6-rc aims to provide mechanism, not policy: it is OS-agnostic and distribution-agnostic. Providing boot scripts, or anything of this kind, would go against this principle; it is -- cgit v1.2.3