/usr/share/doc/samhain/manual.html/controlling-the-daemon.html is in samhain 4.1.4-2build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3. Controlling the daemon</title><link rel="stylesheet" type="text/css" href="docbook.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="The Samhain Host Integrity Monitoring System"><link rel="up" href="usage.html" title="Chapter 3. General usage notes"><link rel="prev" href="daemontool.html" title="2. Using daemontool (or similar utilities)"><link rel="next" href="signals.html" title="4. Signals"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><!--#if expr="! ($HTTP_USER_AGENT = /MSIE/)"--><!--#include virtual="/resources/ssi/header.html"--><!--#endif--><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3. Controlling the daemon</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="daemontool.html">Prev</a> </td><th width="60%" align="center">Chapter 3. General usage notes</th><td width="20%" align="right"> <a accesskey="n" href="signals.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="controlling-the-daemon"></a>3. Controlling the daemon</h2></div></div></div><p>As part of their boot concept, some systems have
individual start/stop scripts for each service (daemon). As a
minimum, these scripts take either 'start' or 'stop' as
argument, sometimes also e.g. 'reload' (to reload the
configuration), 'restart', or 'status' (check whether the
daemon is running). While this is convenient, there are also
a number of problems:</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Some systems do not have such start/stop
scripts.</p></li><li class="listitem"><p>There is no standard for the location of these
scripts.</p></li><li class="listitem"><p>There is no standard for the arguments such a
script may take, neither for their interpretation
(e.g.: on Linux distribution XYZ, do the start/stop
scripts take 'status' as argument, and if, is the
status reported by printing a message or by the exit
status ?)</p></li></ul></div><p>
</p><p>To provide a portable interface for controlling the
<span class="application">samhain</span> daemon, the
executable itself can serve for this purpose (
<span class="emphasis"><em>only if invoked by the superuser</em></span>) The
supported actions, which must be given as
<span class="emphasis"><em>first argument</em></span> on the command line,
are:</p><p>
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
<span class="emphasis"><em>start</em></span> Start
<span class="application">samhain</span>.
Arguments after 'start' are passed to the process.
Daemon mode will be enforced, as well as running in
'check' mode, irrespective of command line or config
file settings.</p></li><li class="listitem"><p>
<span class="emphasis"><em>stop</em></span> Stop the daemon. On Linux and
Solaris, actually all running instances of
<span class="application">samhain</span> are
stopped, even if no pid file is available.</p></li><li class="listitem"><p>
<span class="emphasis"><em>restart</em></span> Stop and start.</p></li><li class="listitem"><p>
<span class="emphasis"><em>reload or force-reload</em></span> Reload the
configuration file.</p></li><li class="listitem"><p>
<span class="emphasis"><em>status</em></span> Check whether the daemon is
running.</p></li></ul></div><p>
</p><p>Success/failure is reported via the exit status as
follows:
<span class="emphasis"><em>0</em></span> Success. (On Linux/Solaris,
<span class="emphasis"><em>stop</em></span> will always be successful, on other
systems only if the pid file is found.)
<span class="emphasis"><em>1</em></span> Unspecified error.
<span class="emphasis"><em>4</em></span> User had insufficient privilege.
<span class="emphasis"><em>5</em></span> Program is not installed.
<span class="emphasis"><em>7</em></span> Program is not running.</p><p>If the
<span class="emphasis"><em>status</em></span> command is given:
<span class="emphasis"><em>0</em></span> Program is running.
<span class="emphasis"><em>1</em></span> Program is dead and /var/run pid file
exists.
<span class="emphasis"><em>3</em></span> Program is stopped.
<span class="emphasis"><em>4</em></span> Program status is unknown.</p><p>I.e., this interface behaves as mandated by the LSB
Standard for init scripts.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="daemontool.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="usage.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="signals.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2. Using daemontool (or similar utilities) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4. Signals</td></tr></table></div><!--#if expr="! ($HTTP_USER_AGENT = /MSIE/)"--><!--#include virtual="/resources/ssi/footer.html"--><!--#endif--></body></html>
|