INN commit: trunk (9 files)
INN Commit
Russ_Allbery at isc.org
Sun Dec 14 17:05:58 UTC 2008
Date: Sunday, December 14, 2008 @ 09:05:57
Author: iulius
Revision: 8232
Be consistent in the documentation: use I<pathbin> and friends
instead of paths like /usr/local/news/bin.
close #5
Modified:
trunk/backends/actmerge.in
trunk/backends/actsync.c
trunk/backends/actsyncd.in
trunk/doc/FAQ
trunk/doc/pod/checklist.pod
trunk/doc/pod/inndf.pod
trunk/doc/pod/innupgrade.pod
trunk/doc/pod/install.pod
trunk/doc/pod/news.daily.pod
------------------------+
backends/actmerge.in | 3 -
backends/actsync.c | 5 +-
backends/actsyncd.in | 3 -
doc/FAQ | 19 +++++-----
doc/pod/checklist.pod | 46 +++++++++++++-----------
doc/pod/inndf.pod | 10 ++---
doc/pod/innupgrade.pod | 4 +-
doc/pod/install.pod | 87 +++++++++++++++++++++++------------------------
doc/pod/news.daily.pod | 2 -
9 files changed, 91 insertions(+), 88 deletions(-)
Modified: backends/actmerge.in
===================================================================
--- backends/actmerge.in 2008-12-14 16:53:54 UTC (rev 8231)
+++ backends/actmerge.in 2008-12-14 17:05:57 UTC (rev 8232)
@@ -1,8 +1,7 @@
#! /bin/sh
# fixscript will replace this line with code to load innshellvars
-# @(#) $Id$
-# @(#) Under RCS control in /usr/local/news/src/inn/local/RCS/actmerge.sh,v
+# $Id$
#
# actmerge - merge two active files
#
Modified: backends/actsync.c
===================================================================
--- backends/actsync.c 2008-12-14 16:53:54 UTC (rev 8231)
+++ backends/actsync.c 2008-12-14 17:05:57 UTC (rev 8232)
@@ -1,6 +1,5 @@
-/* @(#) $Id$ */
-/* @(#) Under RCS control in /usr/local/news/src/inn/local/RCS/actsync.c,v */
-/*
+/* $Id$
+ *
* actsync - sync or merge two active files
*
* usage:
Modified: backends/actsyncd.in
===================================================================
--- backends/actsyncd.in 2008-12-14 16:53:54 UTC (rev 8231)
+++ backends/actsyncd.in 2008-12-14 17:05:57 UTC (rev 8232)
@@ -1,8 +1,7 @@
#! /bin/sh
# fixscript will replace this line with code to load innshellvars
-# @(#) $Id$
-# @(#) Under RCS control in /usr/local/news/src/inn/local/RCS/actsyncd.sh,v
+# $Id$
#
# actsyncd - actsync daemon
#
Modified: doc/FAQ
===================================================================
--- doc/FAQ 2008-12-14 16:53:54 UTC (rev 8231)
+++ doc/FAQ 2008-12-14 17:05:57 UTC (rev 8232)
@@ -549,9 +549,10 @@
INN logs nearly everything except article trace information via syslog.
It expects syslog to write its log messages into particular files under
-~news/log, unless you gave it a different path at configure time. You'll
-need to set up logging of INN-related log messages in your system
-/etc/syslog.conf. See the "Configuring syslog" section in INSTALL.
+~news/log, unless you gave it a different path at configure time (see
+the pathlog parameter in inn.conf). You'll need to set up logging of
+INN-related log messages in your system /etc/syslog.conf. See the
+"Configuring syslog" section in INSTALL.
Note that you don't have to worry about rotating these log files;
news.daily (which should be run nightly from cron) will take care of that
@@ -646,7 +647,7 @@
been fed to that peer.
If a peer doesn't have that article, it's possible that the article is
- spooled on your system somewhere. Check $pathspool/outgoing, or the
+ spooled on your system somewhere. Check $pathoutgoing, or the
innfeed spool if the peer is configured to use innfeed. (It's probably
easier to look for error messages in $pathlog/news.notice than to
actually wade around in $pathspool/innfeed.)
@@ -1103,13 +1104,13 @@
Then try these commands (a variation on commands posted by Katsuhiro
Kondou to inn-workers) on the old server:
- cd pathdb
+ cd <pathdb in inn.conf>
perl -ne 'chomp; ($a,$b,$_) = split " "; print "$_\n" if $_' history \
- | tr . / > pathoutgoing/list
+ | tr . / > <pathoutgoing in inn.conf>/list
innxmit server list
-where pathdb is the path to the directory containing the history file
-(usually ~news/db), pathoutgoing is the path to the outgoing spool
+where <pathdb> is the path to the directory containing the history file
+(usually ~news/db), <pathoutgoing> is the path to the outgoing spool
directory (usually ~news/spool/outgoing), and server is the name of the
new news server to which you're feeding the articles.
@@ -1297,7 +1298,7 @@
#!/bin/sh
echo "100"
- /usr/local/news/bin/inndf -o | awk '{print $1}'
+ <pathbin in inn.conf>/inndf -o | awk '{print $1}'
echo "0"
echo "overview"
Modified: doc/pod/checklist.pod
===================================================================
--- doc/pod/checklist.pod 2008-12-14 16:53:54 UTC (rev 8231)
+++ doc/pod/checklist.pod 2008-12-14 17:05:57 UTC (rev 8232)
@@ -19,6 +19,8 @@
adduser --group --home /usr/local/news news
where F</usr/local/news> is the home directory for the C<news> user.
+This directory will be passed to B<configure> via the B<--prefix>
+option. It will also be set as I<pathnews> in F<inn.conf>.
=item *
@@ -41,7 +43,8 @@
=item *
-If necessary, add F<~news/bin> to the news user's path and F<~news/share/man>
+If necessary, add F<~news/bin> (that is to say I<pathbin>) to the news
+user's path and F<~news/share/man> (that is to say I<pathnews>/share/man)
to the news user's MANPATH in your shell config files. (You may want to
do this, especially the second part, on your regular account; the
man pages are very useful.)
@@ -51,15 +54,15 @@
For bash, try:
- PATH=~news/bin:$PATH
+ PATH=<pathbin in inn.conf>:$PATH
export PATH
- MANPATH=~news/share/man:$MANPATH
+ MANPATH=<pathnews in inn.conf>/share/man:$MANPATH
export MANPATH
or csh:
- setenv PATH ~news/bin:$PATH
- setenv MANPATH ~news/share/man:$MANPATH
+ setenv PATH <pathbin in inn.conf>:$PATH
+ setenv MANPATH <pathnews in inn.conf>/share/man:$MANPATH
although if you don't already have MANPATH set, the above may give an
error or override your defaults (making it so you can only read the news
@@ -83,8 +86,8 @@
Work out configure options (C<./configure --help> for a list). If you
aren't working out of F</usr/local/news>, or want to put some files on a
-different partition, you can set the directories now (or later in
-F<inn.conf> if you change your mind). By default,
+different partition, you can set the directories now (or later in I<pathnews>
+in F<inn.conf> if you change your mind). By default,
B<--prefix=/usr/local/news> is used.
You probably want B<--with-perl>. If you're not using NetBSD with
@@ -124,10 +127,11 @@
=item *
-Now it's time to work on the files in F<~news/etc>. Start with
-F<inn.conf>; you must fill in the default moderators address, your fully
-qualified domain names and path. Fill in all the blanks. Change the
-file descriptor limits to something like C<500>.
+Now it's time to work on the files in F<~news/etc> (the default I<pathetc>
+location set in F<inn.conf>). Start with F<inn.conf>; you must fill
+in the default moderators address, your fully qualified domain names
+and path. Fill in all the blanks. Change the file descriptor limits
+to something like C<500>.
=item *
@@ -161,7 +165,7 @@
=item *
-Run C<~news/bin/inncheck -a -v -f -pedantic -perm> and fix anything noted:
+Run C<< <pathbin in inn.conf>inncheck -a -v -f -pedantic -perm >> and fix anything noted:
B<inncheck> gives a rough check on the appropriateness of the configuration
files as you go. (It's the equivalent of C<perl -cw yourfile.pl> for
Perl scripts.)
@@ -172,7 +176,7 @@
=item *
-You can now import an F<active> file (F<~news/db/active>) and run B<inncheck>
+You can now import an F<active> file (I<pathdb in inn.conf>/active) and run B<inncheck>
again. You may want to look at L<ftp://ftp.isc.org/pub/usenet/CONFIG/active>
and only keep the lines corresponding to the newsgroups you are interested in.
Also import a F<newsgroups> file which contains the descriptions of these
@@ -185,13 +189,13 @@
In case you need to create empty initial database files, import an F<active>
file (owned by C<news>) and execute as the news user:
- cd ~news/db
+ cd <pathdb in inn.conf>
touch newsgroups
touch active.times
touch history
- ~news/bin/makedbz -i
+ <pathbin in inn.conf>/makedbz -i
mv history.n.hash history.hash
mv history.n.index history.index
mv history.n.dir history.dir
@@ -220,12 +224,12 @@
=item *
-Start B<innd> by running F<~news/bin/rc.news> B<as the news user>. It
+Start B<innd> by running I<pathbin>/rc.news B<as the news user>. It
is also what you should launch in your init scripts:
- su news -c ~news/bin/rc.news
+ su news -c <pathbin in inn.conf>/rc.news
-Check F<~news/log/news.notice> to see if everything went well; also use
+Check I<pathlog>/news.notice to see if everything went well; also use
C<ps> to see if B<innd> is running.
C<telnet localhost 119> and you should see either a welcome banner or a
@@ -275,13 +279,13 @@
Begin with auth. Your auth for password users could look like this:
auth "foreignokay" {
- auth: "ckpasswd -d ~news/db/newsusers"
+ auth: "ckpasswd -d <pathdb in inn.conf>/newsusers"
default: "<unauthenticated>"
}
There is a Perl script in the ckpasswd(8) man page if you want to do
authentications by password and have the appropriate libraries. Copy it
-to F<~news/bin>, name the file something like F<makepasswd.pl> and change the
+to I<pathbin>, name the file something like F<makepasswd.pl> and change the
internal paths to whatever you're using and wherever you're putting the
newsusers database. The standard Apache B<htpasswd> tool also works
just fine to create INN password files.
@@ -318,7 +322,7 @@
You then need to start a second B<nnrpd> to listen to these connections
to NNTPS port 563 and put something like that in your init scripts:
- su news -c '~news/bin/nnrpd -D -c ~news/etc/readers-ssl.conf -p 563 -S'
+ su news -c '<pathbin>/nnrpd -D -c <pathetc>/readers-ssl.conf -p 563 -S'
Note that a news client which supports the STARTTLS command can also
use the conventional NNTP port 119 to initiate a TLS connection. However,
Modified: doc/pod/inndf.pod
===================================================================
--- doc/pod/inndf.pod 2008-12-14 16:53:54 UTC (rev 8231)
+++ doc/pod/inndf.pod 2008-12-14 17:05:57 UTC (rev 8232)
@@ -74,18 +74,18 @@
=head1 EXAMPLES
-Print the free kilobytes in F</news/spool> as a simple number:
+Print the free kilobytes in I<pathspool> as a simple number:
- inndf /news/spool
+ inndf <pathspool in inn.conf>
-Report the free inodes in F</usr/local/news> and F</news/spool> in a format
+Report the free inodes in I<pathnews> and I<pathspool> in a format
designed for human readability:
- inndf -i /usr/local/news /news/spool
+ inndf -i <pathnews> <pathspool>
The same, but also add in all file systems in I<pathetc>/filesystems:
- inndf -i -F /usr/local/news /news/spool
+ inndf -i -F <pathnews> <pathspool>
Print out the number of overview records and the percentage space used by
a buffindexed overview database:
Modified: doc/pod/innupgrade.pod
===================================================================
--- doc/pod/innupgrade.pod 2008-12-14 16:53:54 UTC (rev 8231)
+++ doc/pod/innupgrade.pod 2008-12-14 17:05:57 UTC (rev 8232)
@@ -60,9 +60,9 @@
=head1 EXAMPLES
-Upgrade any configuration files found in F</usr/local/news/etc>:
+Upgrade any configuration files found in I<pathetc>:
- innupgrade /usr/local/news/etc
+ innupgrade <pathetc in inn.conf>
Upgrade only F</news/etc/inn.conf>:
Modified: doc/pod/install.pod
===================================================================
--- doc/pod/install.pod 2008-12-14 16:53:54 UTC (rev 8231)
+++ doc/pod/install.pod 2008-12-14 17:05:57 UTC (rev 8232)
@@ -203,6 +203,7 @@
and B<--with-news-group> options to B<configure> (see below). The home
directory of this user should be set to the directory under which you wish
to install INN (F</usr/local/news> is the default and is a good choice).
+This location will be set as I<pathnews> in F<inn.conf>.
INN will install itself as this user and group. You can change these if
you want, but these are the defaults and it's easier to stick with them on
a new installation.
@@ -475,8 +476,8 @@
the directories it needs, change ownerships (if you did not compile as the
news user) and install a setuid program needed to raise resource limits
and allow B<innd> to bind to ports under 1024. This step will install INN
-under the install directory (F</usr/local/news>, unless you specified
-something else to the configure script).
+under the install directory (F</usr/local/news>, known as I<pathnews> in
+F<inn.conf>, unless you specified something else to the configure script).
Exceptionally, if you are installing INN into a directory writable by the
news user, you can run C<make install> as the configured news user. The
@@ -623,28 +624,28 @@
All documentation from this point on assumes that you have set up the news
user on your system as suggested in L<Installing INN> so that the root of
-your INN installation is F<~news>. If you've moved things around by
-using options with C<configure>, you'll need to adjust the instructions to
-account for that.
+your INN installation is F<~news> (I<pathnews> in F<inn.conf>). If you've
+moved things around by using options with C<configure>, you'll need to adjust
+the instructions to account for that.
-All of INN's configuration files are located in F<~news/etc>. Unless
+All of INN's configuration files are located in I<pathetc in inn.conf>. Unless
noted otherwise, any files referred to below are in this directory. When
you first install INN, a sample of each file (containing lots of comments)
-is installed in F<~news/etc>; refer to these for concrete examples of
+is installed in I<pathetc>; refer to these for concrete examples of
everything discussed in this section.
All of INN's configuration files, all of the programs that come with it,
and some of its library routines have documentation in the form of man
-pages. These man pages were installed in F<~news/share/man> as part of the INN
+pages. These man pages were installed in I<pathnews>/share/man as part of the INN
installation process and are the most complete reference to how INN works.
You're strongly encouraged to refer to the man pages frequently while
configuring INN, and for quick reference afterwards. Any detailed
questions about individual configuration files or the behavior of specific
-programs should be answered in them. You may want to add F<~news/share/man> to
+programs should be answered in them. You may want to add I<pathnews>/share/man to
your MANPATH environment variable; otherwise, you may have to use a
command like:
- man -M ~news/share/man inn.conf
+ man -M I<pathnews in inn.conf>/share/man inn.conf
to see the inn.conf(5) man page (for example).
@@ -877,7 +878,7 @@
If the remote site puts its actual hostname in the Path: header, you won't
need the C</news.example.com> part.
-This entry will cause B<innd> to write out a file in F<~news/spool/outgoing>
+This entry will cause B<innd> to write out a file in I<pathspool>/outgoing
named F<remote.example.com> and containing the Message-ID and storage
token of each message to send to that site. (The storage token is INN's
internal pointer to where an article is stored; to retrieve an article
@@ -900,7 +901,7 @@
innfeed!\
:!*\
- :Tc,Wnm*:/usr/local/news/bin/innfeed -y
+ :Tc,Wnm*:<pathbin in inn.conf>/innfeed -y
(adjust the path to innfeed(1) if you installed it elsewhere). Note that
we don't feed this entry any articles directly (its newsgroup pattern is
@@ -928,7 +929,7 @@
imapfeed!\
:!*\
- :Tc,Wnm*,S16384:/usr/local/news/bin/imapfeed
+ :Tc,Wnm*,S16384:<pathbin in inn.conf>/imapfeed
And set up entries for each remote site like:
@@ -947,7 +948,7 @@
controlchan!\
:!*,control,control.*,!control.cancel\
- :AC,Tc,Wnsm:/usr/local/news/bin/controlchan
+ :AC,Tc,Wnsm:<pathbin in inn.conf>/controlchan
(modified for the actual path to B<controlchan> if you put it somewhere
else). See L<Processing Newsgroup Control Messages> for more details.
@@ -1312,7 +1313,7 @@
awk -F: \
'/^cy/ { printf "dd if=/dev/zero of=%s bs=1k count=%s\n", $3, $4 }' \
- /usr/local/news/etc/cycbuff.conf
+ <pathetc in inn.conf>/cycbuff.conf
If you are using block devices, you don't technically have to do anything
at all (since INN is capable of using the devices in F</dev>), but you
@@ -1339,7 +1340,7 @@
=head1 Creating the Database Files
At this point, you need to set up the news database directory
-(F<~news/db>). This directory will hold the active(5) file (the list of
+(in I<pathdb>). This directory will hold the active(5) file (the list of
newsgroups you carry), the active.times(5) file (the creator and creation
time of newsgroups created since the server was initialized), the
newsgroups(5) file (descriptions for all the newsgroups you carry), and
@@ -1351,14 +1352,14 @@
user, since all of these files need to be owned by that user. This is a
good policy to always follow; if you are doing any maintenance work on
your news server, log on as the news user. Don't do maintenance work as
-root. Also make sure that F<~news/bin> is in the default path of the news
-user (and while you're at it, make sure F<~news/share/man> is in the default
+root. Also make sure that I<pathbin> is in the default path of the news
+user (and while you're at it, make sure I<pathnews>/share/man is in the default
MANPATH) so that you can run INN maintenance commands without having to
type the full path.
If you already have a server set up (if you're upgrading, or setting up a
new server based on an existing server), copy F<active> and F<newsgroups>
-from that server into F<~news/db>. Otherwise, you'll need to figure out
+from that server into I<pathdb>. Otherwise, you'll need to figure out
what newsgroups you want to carry and create new active and newsgroups
files for them. If you plan to carry a full feed, or something close to
that, go to L<ftp://ftp.isc.org/pub/usenet/CONFIG/> and download F<active>
@@ -1378,7 +1379,7 @@
Next, you need to create an empty F<history> database. To do this, type:
- cd ~news/db
+ cd <pathdb in inn.conf>
touch history
makedbz -i
@@ -1415,12 +1416,12 @@
Edit F</etc/syslog.conf> on your system and add lines that look like the
following:
- news.crit /usr/local/news/log/news.crit
- news.err /usr/local/news/log/news.err
- news.notice /usr/local/news/log/news.notice
+ news.crit <pathlog in inn.conf>/news.crit
+ news.err <pathlog in inn.conf>/news.err
+ news.notice <pathlog in inn.conf>/news.notice
-(Change the path names as necessary if you installed INN in a different
-location than F</usr/local/news>.) These lines I<must> be tab-delimited,
+(Change the path names as necessary in order to match I<pathlog>, which defaults
+to F</usr/local/news/log>.) These lines I<must> be tab-delimited,
so don't copy and paste from these instructions. Type it in by hand and
make sure you use a tab, or you'll get mysterious failures. You'll also
want to make sure that news log messages don't fill your other log files
@@ -1441,11 +1442,11 @@
time.) Now, make sure that the news log files exist; syslog generally
won't create files automatically. Enter the following commands:
- touch /usr/local/news/log/news.crit
- touch /usr/local/news/log/news.err
- touch /usr/local/news/log/news.notice
- chown news /usr/local/news/log/news.*
- chgrp news /usr/local/news/log/news.*
+ touch <pathlog in inn.conf>/news.crit
+ touch <pathlog in inn.conf>/news.err
+ touch <pathlog in inn.conf>/news.notice
+ chown news <pathlog in inn.conf>/news.*
+ chgrp news <pathlog in inn.conf>/news.*
(again adjusting the paths if necessary for your installation). Finally,
send a HUP signal to syslogd to make it re-read its configuration file.
@@ -1460,12 +1461,12 @@
To run it at 3am, for example, add the following entry to the news user's
crontab file:
- 0 3 * * * /usr/local/news/bin/news.daily expireover lowmark
+ 0 3 * * * <pathbin in inn.conf>/news.daily expireover lowmark
or, if your system does not have per-user crontabs, put the following line
into your system crontab instead:
- 0 3 * * * su -c '/usr/local/news/bin/news.daily expireover lowmark' news
+ 0 3 * * * su -c '<pathbin in inn.conf>/news.daily expireover lowmark' news
If you're using any non-CNFS storage methods, add C<delayrm> to the above
option list for B<news.daily>.
@@ -1480,7 +1481,7 @@
non-empty pending batch files to send pending news to your peers. That
cron entry should look something like:
- 0,10,20,30,40,50 * * * * /usr/local/news/bin/nntpsend
+ 0,10,20,30,40,50 * * * * <pathbin in inn.conf>/nntpsend
The pathnames and user ID used above are the installation defaults; change
them to match your installation if you used something other than the
@@ -1493,11 +1494,11 @@
You may also want to run B<rnews> each hour to process spooled messages
created while B<innd> is not available:
- 12 * * * * /usr/local/news/bin/rnews -U
+ 12 * * * * <pathbin in inn.conf>/rnews -U
And it is also a good practice to refresh each day INN's cached IP addresses:
- 30 2 * * * /usr/local/news/bin/ctlinnd -t 120 -s reload incoming.conf 'flush cache'
+ 30 2 * * * <pathbin in inn.conf>/ctlinnd -t 120 -s reload incoming.conf 'flush cache'
=head1 File Descriptor Limits
@@ -1545,7 +1546,7 @@
news user and not as root. To start INN on system boot, you therefore
want to put something like:
- su news -c /usr/local/news/bin/rc.news
+ su news -c <pathbin in inn.conf>/rc.news
in the system boot scripts. If B<innd> is stopped or killed, you can restart
it by running B<rc.news> by hand as the news user.
@@ -1553,7 +1554,7 @@
The B<rc.news> script may also be used to shut down INN, with the C<stop>
option:
- su news -c '/usr/local/news/bin/rc.news stop'
+ su news -c '<pathbin in inn.conf>/rc.news stop'
In the F<contrib> directory of this source tree is a sample init script
for people using System V-style init.d directories.
@@ -1562,7 +1563,7 @@
B<nnrpd> to listen to these connections to NNTPS port 563 and put something
like that in your init scripts:
- su news -c '/usr/local/news/bin/nnrpd -D -c /usr/local/news/etc/readers-ssl.conf -p 563 -S'
+ su news -c '<pathbin in inn.conf>/nnrpd -D -c <pathetc in inn.conf>/readers-ssl.conf -p 563 -S'
where F<readers-ssl.conf> is the file which indicates whether a given
connection is allowed to read and post news (you can also use the
@@ -1611,24 +1612,24 @@
control messages you want to check.
INN expects the public key ring to either be in the default location for a
-PGP public key ring for the news user (generally F<~news/.gnupg> for GnuPG
-and F<~news/.pgp> for old PGP implementations), or in I<pathetc>/pgp
+PGP public key ring for the news user (generally I<pathnews>/.gnupg for GnuPG
+and I<pathnews>/.pgp for old PGP implementations), or in I<pathetc>/pgp
(F</usr/local/news/etc/pgp> by default). The latter is the recommended path.
To add a key to that key ring, use:
- gpg --import --homedir=/usr/local/news/etc/pgp <file>
+ gpg --import --homedir=<pathetc in inn.conf>/pgp <file>
where <file> is a file containing the hierarchy key. Change the homedir
setting to point to I<pathetc>/pgp if you have INN installed in a non-default
location. If you're using the old-style PGP program, an equivalent
command is:
- env PGPPATH=/usr/local/news/etc/pgp pgp <file>
+ env PGPPATH=<pathetc in inn.conf>/pgp pgp <file>
You can safely answer C<no> to questions about whether you want to sign,
trust, or certify keys. And you may afterwards do:
- cp /usr/local/news/etc/pgp/pubring.gpg /usr/local/news/etc/pgp/trustedkeys.gpg
+ cp <pathetc in inn.conf>/pgp/pubring.gpg <pathetc in inn.conf>/pgp/trustedkeys.gpg
The URLs from which you can get hierarchy keys are noted in comments in
F<control.ctl>. L<ftp://ftp.isc.org/pub/pgpcontrol/PGPKEYS> tries to
Modified: doc/pod/news.daily.pod
===================================================================
--- doc/pod/news.daily.pod 2008-12-14 16:53:54 UTC (rev 8231)
+++ doc/pod/news.daily.pod 2008-12-14 17:05:57 UTC (rev 8232)
@@ -69,7 +69,7 @@
To run it at 3am, for example, add the following entry to the news user's
crontab file:
- 0 3 * * * /usr/local/news/bin/news.daily expireover lowmark
+ 0 3 * * * <pathbin in inn.conf>/news.daily expireover lowmark
If you're using any non-CNFS storage methods, add the B<delayrm> keyword
to the above option list for B<news.daily>.
More information about the inn-committers
mailing list