Commit 15bd521a authored by Per Cederqvist's avatar Per Cederqvist
Browse files

(Parameters): lyskomd is now officially shut down by SIGTERM, not SIGHUP.

(Signals): Ditto.  However, SIGHUP and SIGINT also works.
(Administration): Recommend SIGTERM, not SIGHUP.
(Bugs): Removed entry about terminating on SIGINT and SIGTERM.
parent a352bb45
\input texinfo
@c $Id: lyskomd.texi,v 1.66 2003/08/12 10:36:02 ceder Exp $
@c $Id: lyskomd.texi,v 1.67 2003/08/12 13:13:55 ceder Exp $
@c %**start of header
@setfilename lyskomd.info
@include version.texi
......@@ -444,7 +444,7 @@ about the file format.
@item Status file: @var{path}
This file is created by @code{komrunning} to indicate that lyskomd
should currently not be running. When this file exists
@code{updateLysKOM} will send it a @samp{SIGHUP} signal, so that it
@code{updateLysKOM} will send it a @samp{SIGTERM} signal, so that it
saves the database and dies. Default is @file{etc/status}.
@item Nologin file: @var{path}
......@@ -1026,8 +1026,12 @@ It is possible to control some aspects of lyskomd using Unix signals.
The following signals have special meaning to the server:
@table @samp
@item SIGHUP
Logs out all sessions, saves the database and exits normally.
@item SIGTERM
@itemx SIGHUP
@itemx SIGINT
Logs out all sessions, saves the database and exits normally. Use
@samp{SIGTERM}; the other signals currently have the same
functionality, but that may be changed in the future.
@item SIGQUIT
Saves the database and dump core. (This should only be used for
......@@ -1198,7 +1202,7 @@ which causes the server to write some statistics to a file named
Taking the server down cleanly can be done in two ways: through the use
of the LysKOM protocol on a socket, preferably through the use of a
suitable client, or by sending the signal @samp{SIGHUP} to it. This will
suitable client, or by sending the signal @samp{SIGTERM} to it. This will
cause the server to save the database and close all client
connections. It will also create a file named @file{etc/memory-usage} in
which the memory usage of the server is reported.
......@@ -1242,9 +1246,6 @@ removes the @file{/usr/lyskom/etc/status} file.
@item lyskomd should re-read the config file when a @samp{SIGHUP} is
received.
@item lyskomd should terminate when a @samp{SIGINT} or @samp{SIGTERM} is
received.
@item The security policy is vague and the implementation is frayed at
the edges.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment