rc.news 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 "rc.news stop").
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
If docnfsstat is true in inn.conf: ovdb_init is run;
ovdb_server and ovdb_monitor are stopped.
If rc.news.local exists in pathbin: rc.news.local is run with
argument "start" or "stop" (to perform site-specific startup or shutdown
If the first argument is "start", or no first argument is given,
rc.news initiates INN startup.
If the first argument is "stop", rc.news initiates INN shutdown. It
is recommended to throttle the server first as described in ctlinnd(8).
To start INN and leave certain error messages going to the terminal:
su - news -c <pathbin in inn.conf>/rc.news
To run INN at startup time from appropriate system boot scripts:
su - news -c <pathbin>/rc.news >/dev/console
To stop INN (throttling first):
<pathbin>/ctlinnd throttle reason
su - news -c '<pathbin>/rc.news stop'
Running "rc.news start" as root is never the right thing to do, so we
should at minimum check for this and error, or perhaps change effective
// FIXME: any attribution for rc.news itself?
This manual page written by Jeffrey M. Vinocur <email@example.com> for
$Id: rc.news.pod 8517 2009-06-17 17:49:36Z iulius $