Provided by: inn2_2.6.5-1_amd64 bug

NAME - Start or stop INN daemons

SYNOPSIS ["start" | "stop"]

DESCRIPTION can be used to start or stop innd and supporting programs.  It checks to make sure
       INN is not already running, handles cases of unclean shutdown, finishes up tasks which
       might have been interrupted by the preceding shutdown, e-mails certain boot-time warnings
       to newsmaster (as set in inn.conf), and is generally safer and easier than starting and
       stopping everything directly.  It needs to be run as the news user so that files in
       pathrun are created with the right ownership (though this is less important for "

       Programs run and stopped by this script include:

       ·   Always:  innd is started or stopped.

       ·   If doinnwatch is true in inn.conf:  innwatch is started and stopped.

       ·   If docnfsstat is true in inn.conf:  cnfsstat is started and stopped.

       ·   If ovmethod is set to "ovdb" in inn.conf:  ovdb_init is run; ovdb_server and
           ovdb_monitor are stopped.

       ·   If exists in pathbin: is run with argument "start" or
           "stop" (to perform site-specific startup or shutdown tasks).

       ·   When started, if INN appears to have previously been shut down during its expiry
           process, run expirerm if there are articles to unlink.

       ·   When started, if overview data appears to have just been rebuilt and active needs to
           be renumbered, then actually renumber it.


           If the first argument is "start", or no first argument is given, initiates INN

           If the first argument is "stop", initiates INN shutdown.


       To start INN and leave certain error messages going to the terminal:

              su news -s /bin/sh -c <pathbin in inn.conf>/

       To run INN at startup time from appropriate system boot scripts:

              su news -s /bin/sh -c <pathbin>/ >> <pathlog>/ 2>&1

       To stop INN:

              su news -s /bin/sh -c '<pathbin>/ stop'


       Running " start" as root is never the right thing to do, so we should at minimum
       check for this and error, or perhaps change effective user ID.


       // FIXME:  any attribution for itself?

       This manual page written by Jeffrey M. Vinocur <> for InterNetNews.


       ctlinnd(8), cnfsstat(8), expirerm(8), inn.conf(5), innwatch(8), ovdb(5).