rc.news(8) [redhat man page]

RC.NEWS(8)						    InterNetNews Documentation							RC.NEWS(8)

NAME

       rc.news - Start or stop INN daemons

SYNOPSIS

       rc.news [start | stop]

DESCRIPTION

       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:

       o   Always:  innd is started or stopped.

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

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

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

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

OPTIONS

       "start"
	   If the first argument is "start", or no first argument is given, rc.news initiates INN startup.

       "stop"
	   If the first argument is "stop", rc.news initiates INN shutdown.  It is recommended to throttle the server first as described in
	   ctlinnd(8).

EXAMPLES

       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'

BUGS

       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 user ID.

HISTORY

       // FIXME:  any attribution for rc.news itself?

       This manual page written by Jeffrey M. Vinocur <jeff@litech.org> for InterNetNews.

       $Id: rc.news.pod 9340 2011-08-16 13:50:19Z iulius $

SEE ALSO

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

INN 2.5.3							    2011-08-22								RC.NEWS(8)

OVDB_INIT(8)						    InterNetNews Documentation						      OVDB_INIT(8)

NAME

       ovdb_init - Prepare ovdb database for use

SYNOPSYS

       ovdb_init ["-u"|"-r"]

DESCRIPTION

       This command must be run before any other process can access the overview database.  It performs the following steps:

       1.  Creates the database environment, if necessary

       2.  If the database is idle (and if the "-u" option is not specified), it performs a normal recovery.  The recovery will remove stale
	   locks, recreate the memory pool cache, and repair any damage caused by a system crash or improper shutdown.

       3.  If the "-u" option is specified, it performs any necessary upgrades to the database.  See the UPGRADING section below.

       4.  Starts the DB housekeeping processes (ovdb_monitor) if they're not already running. (Unless the "-r" option is specified).

       5.  Starts the ovdb readserver (ovdb_server) processes if readserver in ovdb.conf is true, and if they are not already running.	(Unless
	   the "-r" option is specified).

       Returns exit status of 0 if all steps were completed successfully.  In the event of an error, messages are written to syslog and/or stderr.

       If a recovery was attempted but it failed, the database may be damaged beyond repair, requiring a rebuild with makehistory(8).

       This command is normally invoked automatically by rc.news(8).

       It is OK to run this command multiple times.

OPTIONS

       "-r"
	   Perform recovery only.  "ovdb_monitor" is not started.

       "-u"
	   Perform any needed upgrades.  Recovery is not attempted.  "ovdb_monitor" is started if the upgrade succeeded.

UPGRADING

       There are two situations in which the database will need to be upgraded:

       o   You upgrade the Berkeley DB library to a newer version, for example from 2.7.7 to 3.1.17.  In this case, the Berkeley DB db->upgrade()
	   method is used.

       o   You upgrade ovdb to a newer major version; i.e., ovdb-1.0 to ovdb-2.0.

       In both of these cases, the database is upgraded in-place; and the upgrade can not be undone.  Do not interrupt the upgrade process once it
       has started, because there is a risk of irrepairable corruption.  The upgrade may take several minutes to complete.  If an upgrade does get
       interrupted, try running the upgrade again.

       Here's an example procedure to upgrade a database created with Berkeley DB 2.7.7 to use Berkeley DB 3.1.17:

       1.  Build and install the Berkeley DB 3.1.17;

       2.  Run configure in the INN source tree and make sure it picks up the right Berkeley DB directory (e.g., /usr/local/BerkeleyDB.3.1);

       3.  Do a "make";

       4.  Shut down INN (e.g., with "rc.news stop") and be sure to kill all instances of nnrpd as well;

       5.  Do a "make update" to install the new binaries;

       6.  Run "ovdb_init -u" as the news user;

       7.  Start INN with "rc.news".

       It is OK to specify "-u" even if no upgrades are needed.

HISTORY

       Written by Heath Kehoe <hakehoe@avalon.net> for InterNetNews.

       $Id: ovdb_init.pod 7851 2008-05-26 19:33:08Z iulius $

SEE ALSO

       ovdb(5), makehistory(8)

INN 2.5.3							    2009-05-21							      OVDB_INIT(8)