From ae97e8065a0e3be60d16c0d9e158afc697aa94e5 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Thu, 5 Apr 2018 09:42:37 +0000 Subject: Add note about SIGINT in s6-svscan and s6-supervise doc --- doc/s6-supervise.html | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'doc/s6-supervise.html') diff --git a/doc/s6-supervise.html b/doc/s6-supervise.html index b2a83d5..d9852b5 100644 --- a/doc/s6-supervise.html +++ b/doc/s6-supervise.html @@ -171,6 +171,17 @@ better to have a collection of service directories single scan directory, and just run s6-svscan on that scan directory. s6-svscan will spawn the necessary s6-supervise processes, and will also take care of logged services. +
  • s6-supervise is not supposed to have a controlling terminal: it's generally +launched by a s6-svscan process that itself does not +have a controlling terminal. If you run s6-supervise from an interactive shell, be +warned that typing ^C in the controlling terminal (which sends a SIGINT to +all processes in the foreground process group in the terminal) will terminate +s6-supervise, but not the supervised processes - so, the daemon will keep running +as an orphan. This is by design: supervised processes should be as resilient as +possible, even when their supervisors die. However, if you want to launch +s6-supervise from an interactive shell and need your service to die when you ^C it, +you can obtain this behaviour by creating a ./nosetsid file in the +service directory.
  • You can use s6-svc to send commands to the s6-supervise process; mostly to change the service state and send signals to the monitored process.
    • -- cgit v1.2.3