From bb9a68add4feef7c53ba3994256745ea99cffef8 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Mon, 20 Mar 2017 20:34:12 +0000
Subject:  Implement permanent failure for services via ./finish exiting 125

---
 doc/s6-supervise.html | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'doc/s6-supervise.html')

diff --git a/doc/s6-supervise.html b/doc/s6-supervise.html
index 081aeae..55cba6f 100644
--- a/doc/s6-supervise.html
+++ b/doc/s6-supervise.html
@@ -56,6 +56,10 @@ s6-supervise kills it with a SIGKILL. This can be configured via the
  <li> When <tt>./finish</tt> dies (or is killed),
 s6-supervise sends a <tt>'D'</tt> event to <tt>./event</tt>. Then
 it restarts <tt>./run</tt> unless it has been told not to. </li>
+ <li> If <tt>./finish</tt> exits 125, then s6-supervise sends a <tt>'O'</tt> event
+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>
  <li> When killed or asked to exit, it waits for the service to go down one last time, then
-- 
cgit v1.3.1