Add -s to s6-rc-init; prepare for 0.3.0.0

1 files changed, 10 insertions, 1 deletions

diff --git a/doc/s6-rc-init.html b/doc/s6-rc-init.html
index f3a7bb1..c531ad6 100644
--- a/doc/s6-rc-init.html
+++ b/doc/s6-rc-init.html
@@ -28,7 +28,7 @@ invocation of the
 <h2> Interface </h2>
 
 <pre>
-     s6-rc-init [ -c <em>compiled</em> ] [ -l <em>live</em> ] [ -t <em>timeout</em> ] [ -b ] <em>scandir</em>
+     s6-rc-init [ -c <em>compiled</em> ] [ -l <em>live</em> ] [ -s <em>suffix</em> ] [ -t <em>timeout</em> ] [ -b ] <em>scandir</em>
 </pre>
 
 <ul>
@@ -74,6 +74,15 @@ filesystem. Default is
 <tt>/run/s6-rc</tt>. The default can be changed at compile time by
 giving the <tt>--livedir=<em>live</em></tt> option to
 <tt>./configure</tt>. </li>
+ <li> <tt>-s&nbsp;<em>suffix</em></tt>&nbsp;: when linking all the
+service directory into <em>scandir</em>, add <em>suffix</em> to the
+names of the symbolic links. This allows several live directories
+to be used with a unique scandir without risking conflicts between
+longruns that would have the same name. This option is only useful
+if you intend to have several sets of services independently managed
+by s6-rc, with different live directories, all using the same scandir
+to supervise their longruns. The default is no suffix at all, which
+is best when you only have one live directory. </li>
  <li> <tt>-b</tt>&nbsp;: blocking lock. If the database is currently
 being used by another program, s6-rc-init will wait until that
 other program has released its lock on the database, then proceed.