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)

INNUPGRADE(8)						    InterNetNews Documentation						     INNUPGRADE(8)

NAME

       innupgrade - Upgrade INN configuration files

SYNOPSIS

       innupgrade directory

       innupgrade [-t type] -f file

DESCRIPTION

       innupgrade is intended to be run during a major upgrade of INN to fix the configuration files with any required changes.  If given a
       directory, it will scan that directory for any files that it has updates defined for, try to perform those updates, and replace the files
       with updated versions if applying the updates resulted in any changes.  The old versions of the files will be saved with a ".OLD"
       extension.

       If the -f flag is used, only that file will be updated.	If the file name doesn't match the standard file name of an INN configuration
       file, the optional -t flag may be given to specify the type.  See "EXAMPLES" for an example of this.

       Currently, innupgrade knows how to apply the following updates:

       inn.conf
	 o Quote values with whitespace and comment out keys with no values, required for the change in configuration parsers introduced in
	   INN 2.4.  The new format is not backward compatible with the previous parser, since the previous parser will include the double-quotes
	   in the value of the parameter.

	 o Add the hismethod parameter if not found (introduced in INN 2.4, with the default value "hisv6") and rename nntpactsync to
	   incominglogfrequency (since INN 2.5).

	 o If the overview.fmt file exists, its content is merged in the extraoverviewadvertised and extraoverviewhidden parameters introduced in
	   INN 2.5.  The file is then renamed to overview.fmt.OLD.

	 o If the sasl.conf file exists, its content is merged in the tlscapath, tlscafile, tlscertfile and tlskeyfile parameters introduced in
	   INN 2.5.   The file is then renamed to sasl.conf.OLD.

       newsfeeds
	 o Replace the use of startinnfeed with the appropriate direct invocation of innfeed or imapfeed.

       A few obsolete programs or configuration files are renamed with a ".OLD" extension by innupgrade.  Obsolete man pages are directly removed.

       Normally, innupgrade should be run at least on the pathetc directory after any upgrade of INN other than a patch release (any upgrade that
       changes the first or second version numbers).  This may occur automatically during the upgrade process.

OPTIONS

       -f file
	   Only act on file rather than working on an entire directory.

       -t type
	   For a file specified with -f, parse it and upgrade it as if it were named type.  Used for upgrading files with the same syntax as
	   normal INN configuration files but with different names.  Only makes sense in combination with -f.

EXAMPLES

       Upgrade any configuration files found in pathetc and append a ".OLD" extension to obsolete files in pathetc:

	   innupgrade <pathetc in inn.conf>

       Upgrade only /news/etc/inn.conf:

	   innupgrade -f /news/etc/inn.conf

       Upgrade a file named inn-special.conf that should have the same syntax as inn.conf:

	   innupgrade -t inn.conf -f inn-special.conf

       Any upgrade rules that apply to inn.conf will be applied to the alternate file.

HISTORY

       Written by Russ Allbery <rra@stanford.edu> for InterNetNews.

       $Id: innupgrade.pod 8415 2009-04-12 20:19:35Z iulius $

INN 2.5.3							    2009-05-21							     INNUPGRADE(8)