/usr/share/doc/samhain/manual.html/controlling-the-daemon.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Controlling the daemon</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="The Samhain Host Integrity Monitoring System"
HREF="index.html"><LINK
REL="UP"
TITLE="General usage notes"
HREF="usage.html"><LINK
REL="PREVIOUS"
TITLE="Using daemontool (or similar utilities)"
HREF="daemontool.html"><LINK
REL="NEXT"
TITLE="Signals"
HREF="signals.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="./docbook.css"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><!--#if expr="! ($HTTP_USER_AGENT = /MSIE/)"--><!--#include virtual="/resources/ssi/header.html"--><!--#endif --><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Samhain Host Integrity Monitoring System</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="daemontool.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. General usage notes</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="signals.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="CONTROLLING-THE-DAEMON"
>3.3. Controlling the daemon</A
></H1
><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
></P
><UL
><LI
><P
>      Some systems do not have such start/stop scripts.
    </P
></LI
><LI
><P
>      There is no standard for the location of these scripts.
    </P
></LI
><LI
><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
>
  </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"
><I
CLASS="EMPHASIS"
>only if invoked by
  the superuser</I
></SPAN
>) The supported actions,
  which must be given as <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>first argument</I
></SPAN
> on 
  the command line, are:
  </P
><P
>  <P
></P
><UL
><LI
><P
>  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>start</I
></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
><P
>  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>stop</I
></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
><P
>  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>restart</I
></SPAN
> Stop and start.
   </P
></LI
><LI
><P
>  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>reload or force-reload</I
></SPAN
> Reload the configuration file.
   </P
></LI
><LI
><P
>  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>status</I
></SPAN
> Check whether the daemon is running.
   </P
></LI
></UL
>
  </P
><P
>Success/failure is reported via the exit status as follows:
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>0</I
></SPAN
> Success. (On Linux/Solaris, 
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>stop</I
></SPAN
> will always 
	be successful, on
	other systems only if the pid file is found.) 
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>1</I
></SPAN
> Unspecified error.
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>4</I
></SPAN
> User had insufficient privilege.
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>5</I
></SPAN
> Program is not installed.
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>7</I
></SPAN
> Program is not running.</P
><P
>If the <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>status</I
></SPAN
> command is given:
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>0</I
></SPAN
> Program is running.
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>1</I
></SPAN
> Program is dead and /var/run pid file exists.
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>3</I
></SPAN
> Program is stopped.
  <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>4</I
></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
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="daemontool.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="signals.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using daemontool (or similar utilities)</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="usage.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Signals</TD
></TR
></TABLE
></DIV
><!--#if expr="! ($HTTP_USER_AGENT = /MSIE/)"--><!--#include virtual="/resources/ssi/footer.html"--><!--#endif --></BODY
></HTML
>
samhain 3.1.0-5ubuntu1 / usr / share / doc / samhain / manual.html / controlling-the-daemon.html
