INN FAQ IV. MAINTENANCE OF INN
IV. MAINTENANCE OF INN
1. Adding new groups - see also Part IV, Section 3.b,:
a. Type: "ctlinnd pause 'edit active'"
b. Edit the active file. The format is:
groupname himark lomark flag.
Set himark to 0000000000 and lomark to 0000000001.
For detailed description of flags, read the man
page for active. Editing the active file by hand
is easy, but will not update the information in
that file active.times that some newsreaders
require to trace new newsgroups. Using ctlinnd
command "newgroup" takes care of this problem
(see below). Editing the active file with an
editor has one drawback - the file active.times
is not automatically updated. This creates problems
for some newsreader (Trumpet being one of them)
that use this file to alert users to new groups.
Using ctlinnd command "newgroup" (see Part IV.3.b)
corrects this problem.
c. Run inncheck (see #11) to check the new active file
d. Type: "ctlinnd reload active 'new active'".
e. Type: "ctlinnd go 'edit active'".
2. New groups are sometimes added automatically through
a control message. A mail message to usenet will alert
to such an automatic change to the active file. If you
do not want to subscribe to a particular news group,
change directory to /usr/local/news and type:
ctlinnd rmgroup <group name>
3. Sometimes, a mail message will arrive for usenet with
a checkgroups file. Remove header, save the body of
the message in:
cd to that directory and type:
Read the output file (todaysdate_pre) and carry out all
the instructions that you think pertain to your
situation. Read the man pages for "active" and
"ctlinnd" for more info. To implement the changes, you
will have to change to the directory: /usr/local/news
a. remove a discontinued group:
type: "ctlinnd rmgroup <group name>"
b. add a group:
type: "ctlinnd newgroup <group name> flag <creator
c. mark a group correctly:
type: "ctlinnd changegroup <group name> flag"
Run inncheck and repeat the docheckgroups command from
the /usr/local/bin/control/news_control directory
Correct any reported problems. Also, you may have to
edit the /usr/local/news/newsgroups file to reflect
any changes you introduced.
4. Read the reports mailed to usenet (you) by the
news.daily script. Most errors are reported here and
should be easy to fix.
5. Subscribe to and read the following newsgroups:
6. IMPORTANT!!! Never run fsck on the drive where the
/spool/news files are located while running INN. Innd
has a lot of active disk I/O going on and you could
corrupt your drive. Use ctlinnd to throttle, pause, or
shutdown innd first - see the manual page for ctlinnd.
[Source:"INN FAQ Part 8"][
[Last Changed:$Date: 1996/01/30 21:44:45 $ $Revision: 2.3 $]
[Copyright: 1996 Norman J. Pieniazek]
INN FAQ Part 8: [Previous]
[Up to Table of Contents]
You can find a summary and links related to this topic
as part of the the Mib Software Usenet RKT.