Next batch of fixes

Signed-off-by: Laurent Bercot <ska@appnovation.com>

4 files changed, 20 insertions, 2 deletions

diff --git a/doc/s6-instance-control.html b/doc/s6-instance-control.html
index cd76688..b52819a 100644
--- a/doc/s6-instance-control.html
+++ b/doc/s6-instance-control.html
@@ -26,7 +26,7 @@ s6-instance-control sends commands to a running instance of an
 <h2> Interface </h2>
 
 <pre>
-     s6-instance-control [ -wu | -wU | -wd | -wD | -wr | -wR ] [ -T <em>timeout</em> ] [ -abqhkti12pcyoduDUxOr ] <em>servicedir</em> <em>name</em>
+     s6-instance-control [ -wu | -wU | -wd | -wD | -wr | -wR ] [ -T <em>timeout</em> ] [ -abqhkti12pcyroduDUxO ] <em>servicedir</em> <em>name</em>
 </pre>
 
 <ul>
diff --git a/doc/s6-instance-create.html b/doc/s6-instance-create.html
index c81dfe4..1aa0d4c 100644
--- a/doc/s6-instance-create.html
+++ b/doc/s6-instance-create.html
@@ -86,6 +86,15 @@ s6-instance-create adds a service directory to that tree and ensures it gets
 supervised. </li>
  <li> If the template for the service is logged, then s6-instance-create will
 wait until supervisors have been spawned for both the instance and its logger. </li>
+ <li> s6-instance-create and <a href="s6-instance-delete.html">s6-instance-delete</a>
+are relatively expensive operations, because they have to recursively copy or
+delete directories and use the <a href="libs6/ftrigr.html">synchronization mechanism</a>
+with the instance supervisor, compared to
+<a href="s6-instance-control.html">s6-instance-control</a> which only has to send
+commands to already existing supervisors. If you are going to turn instances on and
+off on a regular basis, it is more efficient to keep the instance existing and control
+it with <a href="s6-instance-control.html">s6-instance-control</a> than it is to
+repeatedly create and delete it. </li>
 </ul>
 
 </body>
diff --git a/doc/s6-instance-delete.html b/doc/s6-instance-delete.html
index 28eca9c..49530b2 100644
--- a/doc/s6-instance-delete.html
+++ b/doc/s6-instance-delete.html
@@ -66,6 +66,15 @@ on a supervision tree that is specific to the instanced service, and
 s6-instance-delete removes a service directory from that tree. </li>
  <li> If the template for the service is logged, then s6-instance-delete will
 delete both the instance and its logger. </li>
+ <li> s6-instance-delete and <a href="s6-instance-create.html">s6-instance-create</a>
+are relatively expensive operations, because they have to recursively copy or
+delete directories and use the <a href="libs6/ftrigr.html">synchronization mechanism</a>
+with the instance supervisor, compared to
+<a href="s6-instance-control.html">s6-instance-control</a> which only has to send
+commands to already existing supervisors. If you are going to turn instances on and
+off on a regular basis, it is more efficient to keep the instance existing and control
+it with <a href="s6-instance-control.html">s6-instance-control</a> than it is to
+repeatedly create and delete it. </li>
 </ul>
 
 </body>
diff --git a/doc/s6-svc.html b/doc/s6-svc.html
index b8d3c4d..4668a45 100644
--- a/doc/s6-svc.html
+++ b/doc/s6-svc.html
@@ -28,7 +28,7 @@ knowing their PIDs, and without using horrible hacks such as .pid files.
 <h2> Interface </h2>
 
 <pre>
-     s6-svc [ -wu | -wU | -wd | -wD | -wr | -wR ] [ -T <em>timeout</em> ] [ -abqhkti12pcyoduDUxOr ] <em>servicedir</em>
+     s6-svc [ -wu | -wU | -wd | -wD | -wr | -wR ] [ -T <em>timeout</em> ] [ -abqhkti12pcyroduDUxO ] <em>servicedir</em>
 </pre>
 
 <p>