From 04876fbe6bb09832a78b013898d64b3abc921604 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Tue, 4 Oct 2022 19:02:39 +0000
Subject:  s6-supervise QoL: only skip 1-second restart delay when service was
 ready

Signed-off-by: Laurent Bercot <ska@appnovation.com>
---
 doc/s6-supervise.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

(limited to 'doc')

diff --git a/doc/s6-supervise.html b/doc/s6-supervise.html
index 86d97a6..943a347 100644
--- a/doc/s6-supervise.html
+++ b/doc/s6-supervise.html
@@ -171,7 +171,9 @@ to <tt>./event</tt> <em>before</em> the <tt>'D'</tt>, and it
 <strong>does not restart the service</strong>, as if <tt>s6-svc -O</tt> had
 been called. This can be used to signify permanent failure to start the service. </li>
  <li> There is a minimum 1-second delay between two <tt>./run</tt> spawns, to avoid busylooping
-if <tt>./run</tt> exits too quickly. </li>
+if <tt>./run</tt> exits too quickly. If the service has been <em>ready</em> for more
+than one second, it will restart immediately, but if it not <em>ready</em> when
+it dies, s6-supervise will always pause for 1 second before spawning it again. </li>
  <li> When killed or asked to exit, it waits for the service to go down one last time, then
 sends a <tt>'x'</tt> event to <tt>./event</tt> before exiting 0. </li>
 </ul>
-- 
cgit v1.2.3