s6

commit 5fe23e477163ebb42f52a321b178943402011cd8
parent e1b74a19d7de5d781ee0cb5eabc3a667ccf38389
Author: Laurent Bercot <ska-skaware@skarnet.org>
Date:   Fri, 24 Aug 2018 21:51:14 +0000

 Wording clarification on the previous change

Diffstat:
M
doc/s6-supervise.html
 | 
8
++++----

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git 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