info: add a section for signals

Signed-off-by: Mattias Andrée <maandree@operamail.com>

1 files changed, 27 insertions, 0 deletions

diff --git a/info/blueshift.texinfo b/info/blueshift.texinfo
index f398c3b..23d810e 100644
--- a/info/blueshift.texinfo
+++ b/info/blueshift.texinfo
@@ -52,6 +52,7 @@ Texts. A copy of the license is included in the section entitled
 @menu
 * Overview::                        Brief overview of @command{blueshift}.
 * Invoking::                        Invocation of @command{blueshift}.
+* Signals::                         Signals handled by @command{blueshift}.
 * Configuration API::               How to write configuration files.
 * GNU Free Documentation License::  Copying and sharing this manual.
 @end menu
@@ -247,6 +248,32 @@ in relation to each other.
 
 
 
+@node Signals
+@chapter Signals
+
+@command{blueshift}, by default in continuous
+mode, implements special support for three
+signals:
+
+@table @asis
+@item SIGTERM
+Fades out the settings and exits the first
+time SIGTERM is received. If SIGTERM is
+received again, Blueshift immediately
+resets effects and exits.
+
+@kbd{Control+c} is treated as SIGTERM.
+
+@item SIGUSR1
+Reloads the configuration script.
+
+@item SIGUSR2
+Disables or enables Blueshift.
+
+@end table
+
+
+
 @node Configuration API
 @chapter Configuration API