summaryrefslogtreecommitdiffstats
path: root/system/s6/README
diff options
context:
space:
mode:
Diffstat (limited to 'system/s6/README')
-rw-r--r--system/s6/README32
1 files changed, 16 insertions, 16 deletions
diff --git a/system/s6/README b/system/s6/README
index 2c7ec758e3..b7b7c8d67b 100644
--- a/system/s6/README
+++ b/system/s6/README
@@ -1,15 +1,13 @@
s6 is a small suite of programs for UNIX, designed to allow process
-supervision (a.k.a service supervision), in the line of daemontools
-and runit, as well as various operations on processes and daemons. It
-is meant to be a toolbox for low-level process and service
-administration, providing different sets of independent tools that can
-be used within or without the framework, and that can be assembled
-together to achieve powerful functionality with a very small amount of
-code.
+supervision (a.k.a service supervision), in the line of daemontools and
+runit, as well as various operations on processes and daemons. It is
+meant to be a toolbox for low-level process and service administration,
+providing different sets of independent tools that can be used within or
+without the framework, and that can be assembled together to achieve
+powerful functionality with a very small amount of code.
Examples of things you can do by assembling together several programs
provided by s6 - besides process supervision:
-
- syslogd functionality, using much less resources than the traditional
syslogd.
- Reliable service readiness notification, which is the basis for
@@ -21,14 +19,14 @@ provided by s6 - besides process supervision:
without having to switch to any specific init system.
NOTE:
-Upstream recommends building skarnet.org softwares with static libraries
-as most of skarnet.org softwares are small enough that using shared
-libraries are generally not worth using. Therefore, by default, shared
-libraries are not built and binaries are linked against the static
-versions of the skarnet.org libraries.
+Upstream recommends building skarnet.org software with static libraries,
+as most of skarnet.org software are small enough that shared libraries
+are generally not worth using. Therefore, by default, shared libraries
+are not built and binaries are linked against the static versions of the
+skarnet.org libraries.
If you want to also build the shared libraries, pass BUILD_SHARED=yes
-environment variable to the SlackBuild script like below:
+environment variable to this SlackBuild script like below:
BUILD_SHARED=yes ./s6.SlackBuild
@@ -38,8 +36,10 @@ libraries and not the static ones, you can do something like:
BUILD_SHARED=yes BUILD_STATIC=no ./s6.SlackBuild
-If you just want to build and use skarnet.org softwares, building only
+If you just want to build and use skarnet.org software, building only
the static libraries should be sufficient.
If you want the binaries to be linked against the shared versions of the
-skarnet.org libraries, pass LINK_SHARED=yes to the script.
+skarnet.org libraries, pass LINK_SHARED=yes to the script, i.e.,
+
+ LINK_SHARED=yes ./s6.SlackBuild