summaryrefslogtreecommitdiff
path: root/doc/s6-supervise.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/s6-supervise.html')
-rw-r--r--doc/s6-supervise.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/s6-supervise.html b/doc/s6-supervise.html
index 2b5098d..f5cb269 100644
--- a/doc/s6-supervise.html
+++ b/doc/s6-supervise.html
@@ -132,10 +132,10 @@ If it already exists, it uses it as is, without modifying the subscription right
s6-supervise spawns <tt>./run</tt>. </li>
<li> s6-supervise sends a <tt>'u'</tt> event to <tt>./event</tt> whenever it
successfully spawns <tt>./run</tt>. </li>
- <li> If there is a <tt>./notification-fd</tt> file in the service directory
-and s6-supervise is told that the service is ready, it
-sends a <tt>'U'</tt> event to <tt>./event</tt>. There are several ways
-to tell s6-supervise that the service is ready:
+ <li> If there is a <tt>./notification-fd</tt> file in the service directory and,
+at some point after the service has been spawned, s6-supervise is told that the
+service is ready, it sends a <tt>'U'</tt> event to <tt>./event</tt>. There are
+several ways to tell s6-supervise that the service is ready:
<ul>
<li> the daemon may <a href="notifywhenup.html">do so itself</a>. </li>
<li> the run script may have forked a