From 1c44449a9d6accf86f13190c98711dde939b4e6a Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Sat, 22 Feb 2014 08:12:40 +0100 Subject: info: add a section for signals MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- info/blueshift.texinfo | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) 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 -- cgit v1.2.3-70-g09d2