summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2021-01-09 08:34:08 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2021-01-09 08:34:08 +0000
commit2da2bf4e9d509c10a369bce7be364bcbd9af4abb (patch)
tree1e0761d1e14cff0a44e88947cd2c3b3b6a80f399
parentdcde199cad545f33847d94e7bfa662f38559d517 (diff)
downloads6-2da2bf4e9d509c10a369bce7be364bcbd9af4abb.tar.xz
Doc clarification
-rw-r--r--doc/s6-supervise.html4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/s6-supervise.html b/doc/s6-supervise.html
index 94504e3..f116f99 100644
--- a/doc/s6-supervise.html
+++ b/doc/s6-supervise.html
@@ -189,7 +189,9 @@ single <a href="scandir.html">scan directory</a>, and just run
the necessary s6-supervise processes, and will also take care of logged services. </li>
<li> s6-supervise always spawns its child in a new session, as a session leader.
The goal is to protect the supervision tree from misbehaved services that would
-send signals to their whole process group. </li>
+send signals to their whole process group. Nevertheless, s6-supervise's handling of
+SIGINT ensures that its service is killed if you happen to run it in a terminal and
+send it a ^C. </li>
<li> You can use <a href="s6-svc.html">s6-svc</a> to send commands to the s6-supervise
process; mostly to change the service state and send signals to the monitored
process. </li>