From 9811ef53b65027091afc252cba859383419d6c94 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Fri, 13 Nov 2015 13:34:47 +0000
Subject:  - better error codes in s6-rc-update  - doc fixes

---
 doc/s6-rc-update.html | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

(limited to 'doc/s6-rc-update.html')

diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html
index e9ab43c..f683952 100644
--- a/doc/s6-rc-update.html
+++ b/doc/s6-rc-update.html
@@ -59,12 +59,14 @@ live compiled service database. </li>
 
 <ul>
  <li> 0: success </li>
- <li> 1: failure to perform some state transitions </li>
- <li> 2: timed out </li>
+ <li> 1: failure to perform some state transitions, but the database was switched to <em>newdb</em> </li>
+ <li> 2: timed out, but the database was switched to <em>newdb</em> </li>
  <li> 3: unknown service name in the conversion file </li>
  <li> 4: invalid service database </li>
  <li> 5: wrong service type in the conversion file </li>
  <li> 6: duplicate service in the conversion file </li>
+ <li> 9: failure to perform some state transitions, and the database was not switched </li>
+ <li> 10: timed out, and the database was not switched </li>
  <li> 100: wrong usage </li>
  <li> 111: system call failed </li>
 </ul>
@@ -210,11 +212,6 @@ matter whether a service is renamed or not, changing its type will force a
 restart.
 </p>
 
-<tt>ps</tt> output as supervising the old name. This is purely cosmetic and
-will have no impact on the service; nevertheless, if you wish to avoid that,
-simply force a restart on every service you rename.
-</p>
-
 <h4> Restarting </h4>
 
 <p>
-- 
cgit v1.3.1