From 047befef9b8ef074d34b05e294d753f6c2751987 Mon Sep 17 00:00:00 2001
From: Laurent Bercot
Date: Wed, 23 Sep 2015 19:13:22 +0000
Subject: No need for -a in s6-rc -u invocation; remove -X from dryrun print
---
doc/s6-rc.html | 21 ++++++++-------------
1 file changed, 8 insertions(+), 13 deletions(-)
(limited to 'doc/s6-rc.html')
diff --git a/doc/s6-rc.html b/doc/s6-rc.html
index 8eb0753..47afd3f 100644
--- a/doc/s6-rc.html
+++ b/doc/s6-rc.html
@@ -35,8 +35,9 @@ should be achieved by a single s6-rc change invocation.
- s6-rc should only be run as root, especially when asking for a state
-change.
+ Except in test installations with specifically made compiled
+databases and live directories, s6-rc should only be run as root -
+especially when asking for a state change.
Interface
@@ -50,9 +51,7 @@ change.
- s6-rc expects to find a functional live state in
-live (by default /run/s6-rc, unless changed when the package
-was compiled). The live state is
-normally created at boot time by
+live. The live state is normally created at boot time by
s6-rc-init. If the live state is
invalid, s6-rc complains and exits 4.
- Depending on the arguments given, it prints the requested
@@ -78,8 +77,9 @@ state change.
The arguments servicenames... may be atomic services or
bundles; they are resolved into a set of atomic services, which is
called the selection. If the -a option is present,
-the current set of up services is added to the selection.
-The s6-rc command operates on the selection.
+the current set of active services (i.e. services that are up) is
+added to the selection.
+The s6-rc command always operates on the selection.
Options
@@ -95,11 +95,6 @@ giving the --livedir=live option to ./configure. s6-rc -da change
will stop all services.
- - -X : don't lock the live state or the compile
-database. This option should never be used when s6-rc is run
-manually; it's only used by commands such as
-s6-rc-update that spawn a s6-rc
-instance while already holding the necessary locks.
Up or down
@@ -259,7 +254,7 @@ should work with s6-rc with no additional effort.
Oneshot transitions
- Transitions for oneshot services involve running the up
+ Transitions for oneshot services amount to running the up
or down script for the service; those scripts are stored
in the compiled service database that is linked from the live state.
The transition is considered successful if the script exits zero,
--
cgit v1.2.3