Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

inncheck(8) [redhat man page]

INNCHECK(8)						      System Manager's Manual						       INNCHECK(8)

NAME
inncheck - check inn configuration and database files. SYNOPSIS
inncheck [ -a ] [ -v ] [ -pedantic ] [ -f ] [ -perm ] [ -noperm ] [ file=value | file ] DESCRIPTION
Inncheck examines various configuration files and databases and verifies things about them. Things verified depend on the file being checked, but generally are things like permissions, ownership, syntax errors in config files etc. Inncheck does not make changes to any files -- it just reports what it thinks may be wrong, and it is up to the operator to fix the prob- lem. The set of files checked may be restricted by using file or file=value arguments. For example, putting incoming.conf causes only the incom- ing.conf(5) file to be checked. Using incoming.conf=/tmp/incoming.conf on the command line will cause inncheck to only verify the incom- ing.conf file, and it will perform the checks on the file /tmp/incoming.conf file instead of the default one. Valid values for file are: active control.ctl expire.ctl incoming.conf inn.conf moderators newsfeeds overview.fmt nntpsend.ctl passwd.nntp OPTIONS
-a If any ``file'' value or ``file=value'' pairs (see below) are given, then normally only the files they refer to are checked. Use the ``-a'' flag to specify that all files should be checked regardless. In this case the form file=value will be the more useful. -v Use the ``-v'' option to get more verbose output. -pedantic Use the ``-pedantic'' option to get reports on things that are not necessarily wrong, but may indicate a bad configuration -- such as inn.conf(5) missing a key. -f Use the ``-f'' flag to have inncheck print the appropriate chown/chgrp/chmod command necessary to fix a problem that it reports. Any other output lines will be prefixed with a ``#'' character to make the output be valid input for a shell. Note that the ``-perm'' flag must be used as well when using this flag. -perm Inncheck checks all files for permission problems. If the ``-perm'' flag is used, then only the files specified by the file or file=value command line arguments will be checked for problems other than permission problems. -noperm To avoid doing any checking of file permissions or ownership, use the ``-noperm'' option. EXAMPLES
To have inncheck check all files for syntax and permission problems simply: inncheck To have inncheck check all files for permission problems and to verify the syntax of the active and incoming.conf files do: inncheck -perm active incoming.conf To have inncheck check the test newsfeeds file in /var/tmp/newsfeeds.testing, do: inncheck newsfeeds=/var/tmp/newsfeeds.testing To have inncheck check all the files as it normally does, but to specify a different location for the newsfeeds file, so: inncheck -a newsfeeds=/var/tmp/newsfeeds.testing BUGS
If the ``-f'' and ``-perm'' options are used together, along with ``-a'' or some ``file'' or ``file=value'' arguments that refer to a file with a syntax problem, then the output will no longer be valid input for a shell. HISTORY
Written by Brendan Kehoe <brendan@cygnus.com> and Rich Salz <rsalz@uunet.uu.net> This is revision 1.5, dated 1998/10/30. SEE ALSO
active(5), expire.ctl(5), history(5), incoming.conf(5), inn.conf(5), newsfeeds(5) INNCHECK(8)

Check Out this Related Man Page

CONTROLCHAN(8)						      System Manager's Manual						    CONTROLCHAN(8)

NAME
controlchan - channel-fed control message handler SYNOPSIS
controlchan DESCRIPTION
Controlchan removes the responsibility for handling control messages (except cancels) from innd(8) and instead processes them from a chan- nel or file feed. To reduce load, controlchan keeps a copy of control.ctl in memory and checks permissions (including any required PGP headers) before any scripts are called. Also, the default (``bad message'') case is handled internally. The ``drop'' case is handled with far less fuss. Normally, controlchan is invoked by innd(8) as configured in newsfeeds. An example entry is below. Make sure that you've created the newsgroup control.cancel so that controlchan doesn't have to scan through cancels, which it won't process anyway. controlchan! :!*,control,control.*,!control.cancel :AC,Tc,Wnsm :<pathbin in inn.conf>/controlchan Note that in the (very, very unlikely) event that you need to process ihave/sendme control messages, be sure that logipaddr is set to false in inn.conf, because in this case controlchan needs a site name, not an IP address. Controlchan tries to report all log messages through syslog(3), unless connected to an interactive terminal. To enable syslog(3)'ing for versions of Perl prior to 5.6.0, you will need to have run ``h2ph'' on your system include files at some point (this is required to make ``Sys::Syslog'' work). If you have not done so, do this: cd /usr/include h2ph * sys/* If you run FreeBSD, you will need to run the following in addition: h2ph machine/* HISTORY
Written by Katsuhiro Kondou <kondou@nec.co.jp> for InterNetNews. This is revision 8180, dated 2008-11-21. SEE ALSO
control.ctl(5), inn.conf(5). CONTROLCHAN(8)
Man Page