From 9811ef53b65027091afc252cba859383419d6c94 Mon Sep 17 00:00:00 2001
From: Laurent Bercot
Date: Fri, 13 Nov 2015 13:34:47 +0000
Subject: - better error codes in s6-rc-update - doc fixes
---
doc/overview.html | 2 +-
doc/s6-rc-init.html | 6 ++++++
doc/s6-rc-update.html | 11 ++++-------
src/s6-rc/s6-rc-update.c | 8 ++++++--
4 files changed, 17 insertions(+), 10 deletions(-)
diff --git a/doc/overview.html b/doc/overview.html
index 4209f42..12d5e4d 100644
--- a/doc/overview.html
+++ b/doc/overview.html
@@ -195,7 +195,7 @@ managed by s6-rc should be brought down in the proper order (via the
brought down successfully, the final shutdown procedure can take place;
for instance, if s6-svscan is running as process 1 with the
s6-linux-init
-defaults, s6-svscanctl -t /run/service will kill the
+defaults, s6-svscanctl -6 /run/service will kill the
supervision tree and call /etc/rc.shutdown reboot, which should
reboot the machine.
diff --git a/doc/s6-rc-init.html b/doc/s6-rc-init.html
index e5ae884..67ed7de 100644
--- a/doc/s6-rc-init.html
+++ b/doc/s6-rc-init.html
@@ -109,6 +109,12 @@ similarly named, directory (live:suffix)
and updates the live state by atomically changing the target of the
live symlink - so live will not change names, whereas
the real directory may.)
+ Similarly, it is recommended that administrators store their
+compiled service databases into some versioned directory, and that
+compiled be a symbolic link to the database currently in
+use. This will make it easier to create new compiled databases and
+switch them with s6-rc-update
+without having to change the s6-rc-init invocation in boot scripts.