From 958958d74337a6ddaf649968d188e768984100e0 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Tue, 9 Jun 2026 05:27:48 +0000
Subject:  Prepare for 0.6.2.0; implement s6-rc reload

 Also support reload-signal in the service definition directory.
---
 doc/s6-rc.html | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

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

diff --git a/doc/s6-rc.html b/doc/s6-rc.html
index a7eb9d9..bb16113 100644
--- a/doc/s6-rc.html
+++ b/doc/s6-rc.html
@@ -244,6 +244,27 @@ below. It will run the engine to start a set of services.
 below. It will run the engine to stop a set of services.
 </p>
 
+<h3> s6-rc reload </h3>
+
+<p>
+ <tt>s6-rc reload</tt> sends a "reload" command to the list of services
+given on the command line, which must all be up. For a longrun,
+<tt>s6-rc reload</tt> sends an <a href="//skarnet.org/software/s6/s6-svc.html">s6-svc -l</a>
+command to the service, which causes it to receive a SIGHUP, or any
+overriding signal configured in the <tt>reload-signal</tt> file.
+For a oneshot, the service's <tt>up</tt> script is executed, with
+an additional <tt>RC_RELOAD</tt> environment variable containing 1.
+</p>
+
+<p>
+ <tt>s6-rc reload</tt> is special in that it does not use the live state
+at all (except to verify that the services the user wants to reload are
+indeed up) and does not involve the dependency engine. It only operates on
+the services given as arguments on the command line. It is implemented at
+the s6-rc level because it is sometimes useful to ask for a <em>oneshot</em>
+to be reloaded.
+</p>
+
 <h3> s6-rc change </h3>
 
 <p>
-- 
cgit v1.3.1