INN commit: trunk (40 files)

INN Commit Russ_Allbery at isc.org
Sun Sep 2 12:58:08 UTC 2007


    Date: Sunday, September 2, 2007 @ 05:58:07
  Author: iulius
Revision: 7664

Improve paths in checklist.
Improve the items list in cycbuff.conf, INSTALL and storage.conf.
Add a FILES section and "cd <pathdb>" in actsync.
Add a warning for tab-delimitation in newsgroups and newslog.
No space in a uwildmat pattern for clarity in INSTALL.
Use B<--xxx> instead of C<--xxx> for configure options in several files.

Add unbreakable spaces (S<xxx>) to the following expressions:
  ANSI C
  K&R C
  autoconf 2.59
  podlators 1.25
  RFC xxx
  Kerberos v5
  <size> * 1024 bytes
  Perl xxx
  Python xxx
  INN 2.x
  option #x
  Solaris x
  Berkeley DB xxx
  -- (starting and ending clauses between dashes)
  xxx GB/MB/KB

It really improves the reading (especially in HTML and man pages).

Modified:
  trunk/backends/send-uucp.in
  trunk/control/perl-nocem.in
  trunk/doc/pod/active.times.pod
  trunk/doc/pod/actsync.pod
  trunk/doc/pod/archive.pod
  trunk/doc/pod/auth_krb5.pod
  trunk/doc/pod/batcher.pod
  trunk/doc/pod/buffindexed.conf.pod
  trunk/doc/pod/checklist.pod
  trunk/doc/pod/convdate.pod
  trunk/doc/pod/ctlinnd.pod
  trunk/doc/pod/cycbuff.conf.pod
  trunk/doc/pod/fastrm.pod
  trunk/doc/pod/hacking.pod
  trunk/doc/pod/hook-perl.pod
  trunk/doc/pod/hook-python.pod
  trunk/doc/pod/inn.conf.pod
  trunk/doc/pod/innbind.pod
  trunk/doc/pod/innd.pod
  trunk/doc/pod/innupgrade.pod
  trunk/doc/pod/install.pod
  trunk/doc/pod/libinnhist.pod
  trunk/doc/pod/list.pod
  trunk/doc/pod/news.pod
  trunk/doc/pod/newsfeeds.pod
  trunk/doc/pod/newsgroups.pod
  trunk/doc/pod/newslog.pod
  trunk/doc/pod/nnrpd.pod
  trunk/doc/pod/ovdb.pod
  trunk/doc/pod/ovdb_init.pod
  trunk/doc/pod/ovdb_stat.pod
  trunk/doc/pod/passwd.nntp.pod
  trunk/doc/pod/qio.pod
  trunk/doc/pod/radius.pod
  trunk/doc/pod/readme.pod
  trunk/doc/pod/simpleftp.pod
  trunk/doc/pod/storage.conf.pod
  trunk/doc/pod/tdx-util.pod
  trunk/doc/pod/tinyleaf.pod
  trunk/samples/actsync.ign

------------------------------+
 backends/send-uucp.in        |    4 +-
 control/perl-nocem.in        |    2 -
 doc/pod/active.times.pod     |    2 -
 doc/pod/actsync.pod          |   35 +++++++++++++++--
 doc/pod/archive.pod          |    2 -
 doc/pod/auth_krb5.pod        |    8 ++--
 doc/pod/batcher.pod          |    2 -
 doc/pod/buffindexed.conf.pod |   10 ++---
 doc/pod/checklist.pod        |   22 +++++------
 doc/pod/convdate.pod         |    6 +--
 doc/pod/ctlinnd.pod          |    2 -
 doc/pod/cycbuff.conf.pod     |   20 +++++-----
 doc/pod/fastrm.pod           |    4 +-
 doc/pod/hacking.pod          |   22 +++++------
 doc/pod/hook-perl.pod        |    4 +-
 doc/pod/hook-python.pod      |   12 +++---
 doc/pod/inn.conf.pod         |   15 +++----
 doc/pod/innbind.pod          |    6 +--
 doc/pod/innd.pod             |    4 +-
 doc/pod/innupgrade.pod       |    4 +-
 doc/pod/install.pod          |   82 ++++++++++++++++++++---------------------
 doc/pod/libinnhist.pod       |    2 -
 doc/pod/list.pod             |    2 -
 doc/pod/news.pod             |   40 ++++++++++----------
 doc/pod/newsfeeds.pod        |    2 -
 doc/pod/newsgroups.pod       |    4 +-
 doc/pod/newslog.pod          |   11 +++--
 doc/pod/nnrpd.pod            |   10 ++---
 doc/pod/ovdb.pod             |   60 +++++++++++++++---------------
 doc/pod/ovdb_init.pod        |   12 +++---
 doc/pod/ovdb_stat.pod        |   14 +++----
 doc/pod/passwd.nntp.pod      |    2 -
 doc/pod/qio.pod              |    2 -
 doc/pod/radius.pod           |    2 -
 doc/pod/readme.pod           |   18 ++++-----
 doc/pod/simpleftp.pod        |    2 -
 doc/pod/storage.conf.pod     |   16 ++++----
 doc/pod/tdx-util.pod         |    4 +-
 doc/pod/tinyleaf.pod         |    4 +-
 samples/actsync.ign          |    5 +-
 40 files changed, 256 insertions(+), 224 deletions(-)

Modified: backends/send-uucp.in
===================================================================
--- backends/send-uucp.in	2007-08-31 18:03:14 UTC (rev 7663)
+++ backends/send-uucp.in	2007-09-02 12:58:07 UTC (rev 7664)
@@ -348,7 +348,7 @@
 
 This defines eight UUCP sites.  The first three use C<gzip> compression, the
 following site uses C<bzip2> and the last three use C<compress>.  The first
-six use a batch size of 1 MB, and the last site (C<able>) uses the default of
+six use a batch size of S<1 MB>, and the last site (C<able>) uses the default of
 500,000 bytes.  The C<zoetermeer>, C<hoofddorp>, C<pa3ebv>, and C<manhole> sites
 will only have batches generated for them during the hours of 05:00, 18:00,
 and 22:00, and the C<drinkel> site will only have batches generated during those
@@ -360,7 +360,7 @@
 
 As for the F<newsfeeds> file, the usual flags used for a UUCP feed are
 C<Tf,Wnb>.  Here is a typical entry for C<zoetermeer>, where the batching
-is kept between 4 KB and 1 KB:
+is kept between S<4 KB> and S<1 KB>:
 
     zoetermeer\
         :*,!junk,!control/!foo\

Modified: control/perl-nocem.in
===================================================================
--- control/perl-nocem.in	2007-08-31 18:03:14 UTC (rev 7663)
+++ control/perl-nocem.in	2007-09-02 12:58:07 UTC (rev 7664)
@@ -488,7 +488,7 @@
 
 =head1 NAME
 
-perl-nocem - A NoCeM-on-spool implementation for INN 2.x
+perl-nocem - A NoCeM-on-spool implementation for S<INN 2.x>
 
 =head1 SYNOPSIS
 

Modified: doc/pod/active.times.pod
===================================================================
--- doc/pod/active.times.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/active.times.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -29,7 +29,7 @@
 
    news.admin.moderation 1175716803 group-admin at isc.org
 
-shows that the newsgroup news.admin.moderation was created on April 4th 2007
+shows that the newsgroup news.admin.moderation was created on April 4th, 2007,
 at 20:00:03 UTC.  This date can be obtained for instance with
 C<convdate -c 1175716803> (convdate(1) is shipped with INN) or
 C<date -u -d "Jan 1, 1970 00:00:00 +0000 + 1175716803 seconds">.  It is

Modified: doc/pod/actsync.pod
===================================================================
--- doc/pod/actsync.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/actsync.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -136,7 +136,7 @@
 standard output, and write debug messages to standard error.
 
 If the I<debug-format> argument is also given to B<actsyncd>, the data
-written to standard output will be in B<-o> I<debug-format> instead of in
+written to standard output will be in B<-o I<debug-format>> instead of in
 C<-o a1> format.
 
 INN comes with default values of C<ftp.isc.org> for <host> and
@@ -337,7 +337,8 @@
 However, a newsgroup that is equivalent to an ignored newsgroup is not a
 problem.
 
-The default is C<-l 12>: problem newsgroups from both hosts are marked as errors.
+The default is C<-l 12>:  problem newsgroups from both hosts are marked
+as errors.
 
 =item B<-m>
 
@@ -640,7 +641,7 @@
     # moderated or that are under the gnu hierarchy.
     #
     i       *.test
-    c       *.test  m       # check moderated test groups
+    c       *.test m        # check moderated test groups
     c       gnu.*.test
     c       gnu.test        # just in case it ever exists
 
@@ -710,7 +711,7 @@
     actsync - -
 
 To detect any newsgroup errors on your local server, and to remove any
-*.bork.bork.bork style silly newsgroup names:
+*.bork.bork.bork-style silly newsgroup names:
 
     actsync -b 2 - -
 
@@ -720,6 +721,7 @@
 
 is effectively the same as the F<active> file produced by:
 
+    cd <pathdb>
     ctlinnd pause 'running actsync'
     rm -f active.new
     actsync <flags> -o a1 erehwon.honey.edu > active.new
@@ -733,6 +735,31 @@
 simply replacing the F<active> file, may be faster if you are making lots
 of changes.
 
+=head1 FILES
+
+=over 4
+
+=item I<pathbin>/actsync
+
+The C program itself used to synchronize, compare, or merge two F<active>
+files.
+
+=item I<pathbin>/actsyncd
+
+The Shell daemon which provides a convenient interface to configure and
+run B<actsync>.
+
+=item I<pathetc>/actsync.cfg
+
+The configuration file which specifies the settings to use.
+
+=item I<pathetc>/actsync.ign
+
+The ignore file which contains a set of synchronization rules that
+specifies which newsgroups will be checked and which will be ignored.
+
+=back
+
 =head1 CAUTION
 
 Careless use of this tool may result in the unintended addition, change,

Modified: doc/pod/archive.pod
===================================================================
--- doc/pod/archive.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/archive.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -50,7 +50,7 @@
 concatenated into a single file, appending to that file if it already
 exists.  The file name will be C<YYYYMM>, formed from the current time when
 B<archive> is run.  In other words, if given an article in
-comp.sources.unix on December 14, 1998, the article would be appended to
+comp.sources.unix on December 14th, 1998, the article would be appended to
 the file:
 
     comp.sources.unix/199812

Modified: doc/pod/auth_krb5.pod
===================================================================
--- doc/pod/auth_krb5.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/auth_krb5.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -1,6 +1,6 @@
 =head1 NAME
 
-auth_krb5 - nnrpd Kerberos v5 authenticator
+auth_krb5 - nnrpd S<Kerberos v5> authenticator
 
 =head1 SYNOPSIS
 
@@ -8,9 +8,9 @@
 
 =head1 DESCRIPTION
 
-This program does authentication for B<nnrpd> against a Kerberos v5 KDC.
+This program does authentication for B<nnrpd> against a S<Kerberos v5 KDC>.
 This is NOT real Kerberos authentication using service tickets; instead, a
-username and password is used to attempt to obtain a Kerberos v5 TGT to
+username and password is used to attempt to obtain a S<Kerberos v5 TGT> to
 confirm that they are valid.  As such, this authenticator assumes that
 B<nnrpd> has been given the user's username and password, and therefore is
 not as secure as real Kerberos authentication.  It generally should only
@@ -38,7 +38,7 @@
 =head1 EXAMPLE
 
 The following readers.conf(5) fragment tells nnrpd to authenticate users
-by attempting to obtain Kerberos v5 TGTs for them, appending an instance
+by attempting to obtain S<Kerberos v5 TGTs> for them, appending an instance
 of C<nntp> to usernames before doing so:
 
     auth kerberos {

Modified: doc/pod/batcher.pod
===================================================================
--- doc/pod/batcher.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/batcher.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -53,7 +53,7 @@
 
 This flag sets the size limit for each batch; as soon as at least this
 much data has been written out, a new batch will be started.  The default
-size is 60KB.  Using C<-b 0> will allow unlimited batch sizes.
+size is S<60 KB>.  Using C<-b 0> will allow unlimited batch sizes.
 
 =item B<-B> I<total-size>
 

Modified: doc/pod/buffindexed.conf.pod
===================================================================
--- doc/pod/buffindexed.conf.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/buffindexed.conf.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -9,7 +9,7 @@
 buffindexed (as configured by the I<ovmethod> parameter in F<inn.conf>).
 
 Buffindexed uses pre-built buffer files to store overview data and indexes
-to that data.  The buffers are divided into 8KB internally, and a given
+to that data.  The buffers are divided into S<8 KB> internally, and a given
 block is used either for overview data or for index data.  A block is
 always allocated to a single newsgroup and is never shared among
 newsgroups.
@@ -44,10 +44,10 @@
 <filename> is the path to the buffer.  The length of the path should not
 be longer than 63 characters.
 
-<size> is the length of the buffer in kilobytes (1KB = 1024 bytes).  If
+<size> is the length of the buffer in kilobytes (S<1 KB = 1024 bytes>).  If
 <filename> does not specify a special device, the file size of the buffer
-must be <size> * 1024 bytes.  If it does specify a special device, that
-device must have at least <size> space available.  Buffers over 2GB are
+must be S<< <size> * 1024 bytes >>.  If it does specify a special device, that
+device must have at least <size> space available.  Buffers over S<2 GB> are
 not supported (regardless of whether INN was compiled with large file
 support); this limitation may be fixed in the future.  For more
 information on setting up the buffers, see L<CREATING BUFFERS>.
@@ -97,7 +97,7 @@
 locking on block devices, and therefore this method should not be used on
 Solaris.
 
-Partition the disk to make each partition equal to or smaller than 2GB.
+Partition the disk to make each partition equal to or smaller than S<2 GB>.
 If you're using Solaris, set up your partitions to avoid the first
 cylinder of the disk (or otherwise the buffindexed header will overwrite
 the disk partition table and render the buffers inaccessible).  Then,

Modified: doc/pod/checklist.pod
===================================================================
--- doc/pod/checklist.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/checklist.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -18,7 +18,7 @@
 
     adduser --group --home /usr/local/news news
 
-where F</usr/local/news/> is the home directory for the C<news> user.
+where F</usr/local/news> is the home directory for the C<news> user.
 
 =item *
 
@@ -31,7 +31,7 @@
 are owned by C<news>, group C<news>.
 
 You want to be careful that things in that directory stay owned by
-C<news> -- but you can't just C<chown -R news.news> after the install,
+C<news> S<-- but> you can't just C<chown -R news.news> after the install,
 because you may have binaries that are SUID root.  You can do the build
 as any user, but you need to be root when doing C<make install> so as
 to set the permissions correctly.  After that point, though, you may
@@ -85,11 +85,11 @@
 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,
-C<--prefix=/usr/local/news> is used.
+B<--prefix=/usr/local/news> is used.
 
-You probably want C<--with-perl>.  If you're not using NetBSD with
-cycbuffs or OpenBSD, perhaps C<--with-tagged-hash>.  You might want to
-compile in SSL and Berkeley DB, if your system supports them.  You
+You probably want B<--with-perl>.  If you're not using NetBSD with
+cycbuffs or OpenBSD, perhaps B<--with-tagged-hash>.  You might want to
+compile in SSL and S<Berkeley DB>, if your system supports them.  You
 will need to have the relevant external libraries to compile (depending
 on whether you use OpenSSL for TLS/SSL access to your news server, GnuPG
 to verify the authenticity of Usenet control messages, Perl, Python, etc.).
@@ -118,13 +118,13 @@
 =item *
 
 Find F<INSTALL> and open a separate window for it.  A printout is
-probably a good idea -- it's long but very helpful.  Any time the
+probably a good idea S<-- it's> long but very helpful.  Any time the
 instructions below ask you to make a decision, you can probably find
 help in F<INSTALL>.
 
 =item *
 
-Now it's time to work on the files in F<~news/etc/>.  Start with
+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>.
@@ -223,7 +223,7 @@
 Start B<innd> by running F<~news/bin/rc.news> B<as the news user>.  It
 is also what you should launch in your init scripts:
 
-    su news -c /usr/local/news/bin/rc.news
+    su news -c ~news/bin/rc.news
 
 Check F<~news/log/news.notice> to see if everything went well; also use
 C<ps> to see if B<innd> is running.
@@ -249,7 +249,7 @@
 
 To get your incoming feeds working, edit F<incoming.conf>.  When done,
 C<ctlinnd reload incoming.conf 'reason'> (where C<reason> is some text
-that will show up in the logs -- anything will do).
+that will show up in the logs S<-- anything> will do).
 
 =item *
 
@@ -318,7 +318,7 @@
 You then need to start a second B<nnrpd> to listen to these connections
 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 '~news/bin/nnrpd -D -c ~news/etc/readers-ssl.conf -p 563 -S'
 
 =back
 

Modified: doc/pod/convdate.pod
===================================================================
--- doc/pod/convdate.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/convdate.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -1,6 +1,6 @@
 =head1 NAME
 
-convdate - Convert to/from RFC 2822 dates and seconds since epoch
+convdate - Convert to/from S<RFC 2822> dates and seconds since epoch
 
 =head1 SYNOPSIS
 
@@ -10,7 +10,7 @@
 
 B<convdate> translates the date/time strings given on the command line,
 outputting the results one to a line.  The input can either be a date in
-RFC 2822 format (accepting the variations on that format that innd(8) is
+S<RFC 2822> format (accepting the variations on that format that innd(8) is
 willing to accept), or the number of seconds since epoch (if B<-c> is
 given).  The output is either ctime(3) results, the number of seconds
 since epoch, or a Usenet Date: header, depending on the options given.
@@ -48,7 +48,7 @@
 
 =item B<-s>
 
-Pass each given date to the RFC 2822 date parser and print the results of
+Pass each given date to the S<RFC 2822> date parser and print the results of
 ctime(3) (or a Date: header if B<-d> is given).  This is the default
 behavior.
 

Modified: doc/pod/ctlinnd.pod
===================================================================
--- doc/pod/ctlinnd.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/ctlinnd.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -477,7 +477,7 @@
 B<ctlinnd> uses Unix domain sockets on most systems to communicate with
 B<innd> and is therefore limited by whatever maximum packet size the
 operating system imposes on Unix domain datagrams.  This may mean that
-server replies are limited to 4KB on some systems.
+server replies are limited to S<4 KB> on some systems.
 
 =head1 HISTORY
 

Modified: doc/pod/cycbuff.conf.pod
===================================================================
--- doc/pod/cycbuff.conf.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/cycbuff.conf.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -17,7 +17,7 @@
 C<sequential> mode is specified, in which case each cycbuff is filled
 before moving on to the next).  This is so that you can distribute the
 individual cycbuffs across multiple physical disks and balance the load
-between them.  Note that in order to use any cycbuff larger than 2 GB,
+between them.  Note that in order to use any cycbuff larger than S<2 GB>,
 you need to build INN with the B<--enable-largefiles> option.
 
 For information about how to configure INN to use CNFS, see
@@ -38,7 +38,7 @@
 
 =over 4
 
-=item cycbuffupdate:<interval>
+=item I<cycbuffupdate>:<interval>
 
 Sets the number of articles written before the cycbuff header is
 written back to disk to <interval>.  Under most operating systems, the
@@ -50,25 +50,25 @@
 default value, if this line is omitted, is C<25>, meaning that the header is
 written to disk after every 25 articles stored in that cycbuff.
 
-=item refreshinterval:<interval>
+=item I<refreshinterval>:<interval>
 
 Sets the interval (in seconds) between re-reads of the cycbuff header to
 <interval>.  This primarily affects B<nnrpd> and controls the frequency
 with which it updates its knowledge of the current contents of the CNFS
 cycbuffs.  The default value, if this line is omitted, is C<30>.
 
-=item cycbuff:<name>:<file>:<size>
+=item I<cycbuff>:<name>:<file>:<size>
 
 Configures a particular CNFS cycbuff.  <name> is a symbolic name for the
 buffer, to be used later in a metacycbuff line.  It must be no longer than
 seven characters.  <file> is the full path to the buffer file or block
 device, and must be no longer than 63 characters.  <size> is the length of
-the buffer in kilobytes (1KB is 1024 bytes).  If <file> is not a block
-device, it should be <size> * 1024 bytes long.
+the buffer in kilobytes (S<1 KB> is 1024 bytes).  If <file> is not a block
+device, it should be S<< <size> * 1024 bytes >> long.
 
-If you're trying to stay under 2 GB, keep your sizes below C<2097152>.
+If you're trying to stay under S<2 GB>, keep your sizes below C<2097152>.
 
-=item metacycbuff:<name>:<buffer>[,<buffer>,...][:<mode>]
+=item I<metacycbuff>:<name>:<buffer>[,<buffer>,...][:<mode>]
 
 Specifies a collection of CNFS buffers that make up a single logical
 storage location from the perspective of INN.  Metacycbuffs are referred
@@ -148,10 +148,10 @@
 mmap() on block devices (Solaris and recent versions of Linux do, FreeBSD
 at last report does not), this is the recommended method since you can
 avoid all of the native file system overhead.  Note, however, that each
-cycbuff cannot be larger than 2GB with this method, so if you need a lot
+cycbuff cannot be larger than S<2 GB> with this method, so if you need a lot
 of spool space, you may have to go back to disk files.
 
-Partition the disk to make each partition equal to or smaller than 2GB.
+Partition the disk to make each partition equal to or smaller than S<2 GB>.
 If you're using Solaris, set up your partitions to avoid the first
 cylinder of the disk (or otherwise the cycbuff header will overwrite the
 disk partition table and render the cycbuffs inaccessible).  Then, create

Modified: doc/pod/fastrm.pod
===================================================================
--- doc/pod/fastrm.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/fastrm.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -37,8 +37,8 @@
 systems, root is allowed to unlink directories, even directories which
 aren't empty, which can cause file system corruption.)
 
-The input to B<fastrm> should always be sorted -- or even better be in the
-order file names are output by find(1) -- if speed is an issue and the
+The input to B<fastrm> should always be sorted S<-- or> even better be in the
+order file names are output by S<find(1) --> if speed is an issue and the
 input isn't solely storage API tokens.  (It deals fine with unsorted
 input, but is unlikely to be any faster in that case than a simple C<xargs
 rm> command.)  Sorting may even slightly speed up the removal of storage

Modified: doc/pod/hacking.pod
===================================================================
--- doc/pod/hacking.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/hacking.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -17,8 +17,8 @@
 
     <http://inn.eyrie.org/viewcvs>
 
-You will need Autoconf 2.59 or later to use the development tree.  After
-checking out the tree, run C<./autogen> to generate the necessary Autoconf
+You will need S<autoconf 2.59> or later to use the development tree.  After
+checking out the tree, run C<./autogen> to generate the necessary autoconf
 files.
 
 Nightly snapshots and repository dumps suitable for use with svk will be
@@ -26,7 +26,7 @@
 
 =head1 Configuring and Portability
 
-All INN code should be written expecting ANSI C and POSIX.  There is no
+All INN code should be written expecting S<ANSI C> and POSIX.  There is no
 need to attempt to support pre-ANSI compilers, and ANSI-only features such
 as <stdarg.h>, string concatenation, #elif, and token pasting may be used
 freely.  So far as possible, INN is written to attempt to be portable to
@@ -35,7 +35,7 @@
 checking for standard behavior in configure and supplying replacements for
 standard functions that are missing.
 
-When there is a conflict between ANSI C and C99, INN code should be
+When there is a conflict between S<ANSI C> and C99, INN code should be
 written expecting C99 and autoconf used to patch up the differences.
 
 Try to avoid using #ifdef and the like in the middle of code as much as
@@ -63,7 +63,7 @@
 instead, note in your patch that those files must be regenerated.  These
 (and all other) generated files should not be checked into Subversion.
 
-At the time of this writing, autoconf 2.59 or later is required.
+At the time of this writing, S<autoconf 2.59> or later is required.
 
 The supporting files for autoconf are in the F<support> subdirectory,
 including the files F<config.guess> and F<config.sub> to determine the
@@ -111,7 +111,7 @@
 latest version of podlators.  For versions of Perl earlier than 5.005,
 you'll also need File::Spec in F<modules/by-module/File>.
 
-podlators 1.25 or later will build INN's documentation without significant
+S<podlators 1.25> or later will build INN's documentation without significant
 changes from the versions that are checked into the repository.
 
 There are Makefile rules in F<doc/pod/Makefile> to build all of the
@@ -341,7 +341,7 @@
 provides macros that INN assumes are available but which weren't found,
 and defines some additional portability things.  Even if this is more
 headers than the source file actually needs, it's generally better to just
-include F<clibrary.h> rather than trying to duplicate the Autoconf-driven
+include F<clibrary.h> rather than trying to duplicate the autoconf-driven
 hackery that it does to do things portably.  The primary exception is for
 source files in lib that only define a single function and are used for
 portability; those may want to include only F<config.h> so that they can
@@ -412,12 +412,12 @@
 
 =item *
 
-Write in regular ANSI C whenever possible.  Use the normal ANSI and POSIX
+Write in regular S<ANSI C> whenever possible.  Use the normal ANSI and POSIX
 constructs and use autoconf or portability wrappers to fix things up
 beforehand so that the code itself can read like regular ANSI or POSIX
 code.  Code should be written so that it works as expected on a modern
 platform and is fixed up with portability tricks for older platforms, not
-the other way around.  You may assume an ANSI C compiler.
+the other way around.  You may assume an S<ANSI C> compiler.
 
 Try to use const wherever appropriate.  Don't use register; modern
 compilers will do as good of a job as you will in choosing what to put
@@ -689,8 +689,8 @@
 =item <http://www.imc.org/ietf-usefor/>
 
 The archives for the USEFOR IETF working group, the working group for the
-RFC 1036 replacement (the format of Usenet articles).  Also contains a lot
-of references to other relevant work, such as the RFC 822 replacement
+S<RFC 1036> replacement (the format of Usenet articles).  Also contains a lot
+of references to other relevant work, such as the S<RFC 822> replacement
 work.
 
 =item <http://www.mibsoftware.com/userkt/inn/dev/>

Modified: doc/pod/hook-perl.pod
===================================================================
--- doc/pod/hook-perl.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/hook-perl.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -19,7 +19,7 @@
 The Perl authentication hooks allow you to replace or supplement the
 readers.conf mechanism used by nnrpd.
 
-For Perl filtering support, you need to have Perl version 5.004 or newer.
+For Perl filtering support, you need to have Perl S<version 5.004> or newer.
 Earlier versions of Perl will fail with a link error at compilation time.
 http://language.perl.com/info/software.html should have the latest Perl
 version.
@@ -62,7 +62,7 @@
 only once when innd first starts.  That makes it the ideal place to put
 initialization code that should only run once, or code to load data that
 was preserved on disk across a stop and restart of innd (perhaps using
-filter_mode() -- see below).
+filter_mode() S<-- see> below).
 
 As mentioned above, C<ctlinnd reload filter.perl> (or C<ctlinnd reload
 all>) will cause F<filter_innd.pl> to be reloaded.  If the function

Modified: doc/pod/hook-python.pod
===================================================================
--- doc/pod/hook-python.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/hook-python.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -6,7 +6,7 @@
 filtering.  It is patterned after the TCL and Perl hooks previously added
 by Bob Heiney and Christophe Wolfhugel.
 
-For this filter to work successfully, you will need to have Python 1.5.2
+For this filter to work successfully, you will need to have S<Python 1.5.2>
 (the latest at this writing) installed.  You can obtain it from
 <http://www.python.org>.
 
@@ -21,14 +21,14 @@
 libraries required for embedding into INN.  You will need to add the
 development package.  Better yet, get the source kit from the above URL
 and build it yourself.  Be sure when installing Python on Red Hat, to run
-configure with C<--prefix=/usr> so that there are no version conflicts
+configure with B<--prefix=/usr> so that there are no version conflicts
 with the "factory" installation.  You can also find a selection of well
 made RPMs at <ftp://starship.python.net/pub/crew/andrich/>.
 
 =head1 INSTALLATION
 
 Once you have built and installed Python, you can cause INN to use it by
-adding the C<--with-python> switch to your configure command.
+adding the B<--with-python> switch to your configure command.
 
 See the ctlinnd(8) manual page to learn how to enable, disable and reload
 Python filters on a running server (C<ctlinnd mode>, C<ctlinnd python
@@ -109,7 +109,7 @@
 command, this function can be used to do something sensible in accordance
 with the state change.  Stamp a log file, save your state on throttle,
 etc.  oldmode and newmode will be strings containing one of the values in
-('running', 'throttled', 'paused', 'shutdown', 'unknown') -- oldmode is
+('running', 'throttled', 'paused', 'shutdown', 'unknown') S<-- oldmode> is
 the state innd was in before ctlinnd was run, newmode is the state innd
 will be in after the command finishes.  reason is the comment string
 provided on the ctlinnd command line.
@@ -159,7 +159,7 @@
 
 =head1 WHAT'S THE DEAL WITH THESE BUFFER OBJECTS?
 
-Buffer objects are cousins of strings, new in Python 1.5.2.  They are
+Buffer objects are cousins of strings, new in S<Python 1.5.2>.  They are
 supported, but at this writing you won't yet find much about them in the
 Python documentation.  Using buffer objects may take some getting used to,
 but we can create buffers much faster and with less memory than strings.
@@ -345,7 +345,7 @@
 
 Python authentication, dynamic access group generation and dynamic
 access control support in nnrpd along with filtering support in innd
-may be compiled in by passing C<--with-python> C<configure>.
+may be compiled in by passing B<--with-python> C<configure>.
 
 Support for authentication via Python is provided in nnrpd by the
 inclusion of a python_auth: parameter in a F<readers.conf> auth

Modified: doc/pod/inn.conf.pod
===================================================================
--- doc/pod/inn.conf.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/inn.conf.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -200,7 +200,7 @@
 The maximum size of article (headers and body) that will be accepted by
 the server, in bytes.  A value of C<0> allows any size of article, but
 note that B<innd> will crash if system memory is exceeded.  The default
-value is C<1000000> (approximately 1 MB).  This is checked against the
+value is C<1000000> (approximately S<1 MB>).  This is checked against the
 article in wire format (CRLF at the end of each line, leading periods
 protected, and with the trailing "\r\n.\r\n" at the end).  See also
 I<localmaxartsize>.
@@ -262,7 +262,7 @@
 =item I<sourceaddress>
 
 Which local IP address to bind to for outgoing NNTP sockets (used by
-innxmit(8) among other programs, but I<not> innfeed(8) -- see
+innxmit(8) among other programs, but I<not> innfeed(8) S<-- see>
 I<bindaddress> in innfeed.conf(5) for that).  This must be in dotted-quad
 format (nnn.nnn.nnn.nnn).  If set to C<all> or not set, the operating
 system will choose the source IP address for outgoing connections.  The
@@ -402,7 +402,7 @@
 
 =item C<ovdb>
 
-Stores data into a Berkeley DB database.  See the ovdb(5) man page.
+Stores data into a S<Berkeley DB> database.  See the ovdb(5) man page.
 
 =back
 
@@ -675,7 +675,7 @@
 
 Articles larger than this value in bytes will not have keywords generated
 for them (since it would take too long to do so).  The default value is
-C<100000> (approximately 100 KB).
+C<100000> (approximately S<100 KB>).
 
 =item I<keylimit>
 
@@ -747,8 +747,7 @@
 larger than this will be rejected.  A value of C<0> allows any size of
 article, but note that B<nnrpd> and B<innd> will crash if system memory is
 exceeded.  See also I<maxartsize>, which applies to all articles including
-those posted locally.  The default value is C<1000000> (approximately 1
-MB).
+those posted locally.  The default value is C<1000000> (approximately S<1 MB>).
 
 =item I<moderatormailer>
 
@@ -1097,8 +1096,8 @@
 newsgroups like control.cancel, this may cause too much mmapping at once
 leading to system resource problems.  To avoid this, if the amount to be
 mmapped exceeds I<keepmmappedthreshold> (in KB), buffindexed mmap's just
-one overview block (8 KB).  This parameter is specific to buffindexed
-overview storage method.  The default value is C<1024> (1 MB).
+one overview block (S<8 KB>).  This parameter is specific to buffindexed
+overview storage method.  The default value is C<1024> (S<1 MB>).
 
 =item I<maxcmdreadsize>
 

Modified: doc/pod/innbind.pod
===================================================================
--- doc/pod/innbind.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/innbind.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -30,7 +30,7 @@
 address.  To bind to all addresses with IPv6, use C<::> as the address.
 
 Multiple arguments can be specified to tell B<innbind> to bind multiple
-sockets at the same time.  Any errors (other than permission denied -- see
+sockets at the same time.  Any errors (other than permission denied S<-- see>
 below) encountered will cause B<innbind> to abort, and error messages will
 be sent both to syslog and to standard error.
 
@@ -152,8 +152,8 @@
 =item invalid IPv6 address %s in %s
 
 (Fatal) The IPv6 address specified in the given command-line option could
-not be parsed by inet_pton(3).  IPv6 addresses should be specified in RFC
-2373 format (1080:0:0:0:8:800:200C:417A or 1080::8:800:200C:417A).
+not be parsed by inet_pton(3).  IPv6 addresses should be specified in S<RFC
+2373> format (1080:0:0:0:8:800:200C:417A or 1080::8:800:200C:417A).
 
 =item invalid command-line argument %s
 

Modified: doc/pod/innd.pod
===================================================================
--- doc/pod/innd.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/innd.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -70,7 +70,7 @@
 Only applies when INN has been built with IPv6 support.  Normally B<innd>
 binds to all local IP addresses (unless I<bindaddress6> is set in
 F<inn.conf>).  If this option is given, it specifies the IPv6 address that
-INN should bind to.  The IPv6 address must be in colon-separated RFC 2373
+INN should bind to.  The IPv6 address must be in colon-separated S<RFC 2373>
 format (C<n:n:n:n:n:n:n:n>).
 
 If this option is specified, it's the same as setting I<bindaddress6> in
@@ -285,7 +285,7 @@
 
 =head1 PROTOCOL DIFFERENCES
 
-B<innd> implements the NNTP commands defined in RFC 977, with the
+B<innd> implements the NNTP commands defined in S<RFC 977>, with the
 following differences:
 
 =over 4

Modified: doc/pod/innupgrade.pod
===================================================================
--- doc/pod/innupgrade.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/innupgrade.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -29,8 +29,8 @@
 =item *
 
 F<inn.conf>:  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,
+values, required for the change in configuration parsers introduced in S<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.
 

Modified: doc/pod/install.pod
===================================================================
--- doc/pod/install.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/install.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -1,4 +1,4 @@
-=head1 Welcome to INN 2.5!
+=head1 Welcome to S<INN 2.5>!
 
 Please read this document thoroughly before trying to install INN.  You'll
 be glad you did.
@@ -11,7 +11,7 @@
 try to update your old installation.  This is particularly true if you're
 upgrading from a version of INN prior to 2.0.
 
-If you are upgrading from INN 2.3 or later, you may be able to just update
+If you are upgrading from S<INN 2.3> or later, you may be able to just update
 the binaries, scripts, and man pages by running:
 
     make update
@@ -70,9 +70,9 @@
 
 =item *
 
-In order to build INN, you will need a C compiler that understands ANSI C.
+In order to build INN, you will need a C compiler that understands S<ANSI C>.
 If you are trying to install INN on an operating system that doesn't have
-an ANSI C compiler (such as SunOS), installing B<gcc> is recommended.  You
+an S<ANSI C> compiler (such as SunOS), installing B<gcc> is recommended.  You
 can get it from L<ftp://ftp.gnu.org/gnu/gcc/> or its mirrors.  INN is
 tested with B<gcc> more thoroughly than with any other compiler, so even if
 you have another compiler available, you may wish to use B<gcc> instead.
@@ -85,7 +85,7 @@
 
 =item *
 
-INN requires at least B<Perl 5.004_03> to build and to run several
+INN requires at least S<B<Perl 5.004_03>> to build and to run several
 subsystems.  INN is tested primarily with newer versions of Perl, so it's
 generally recommended that you install the latest stable distribution of
 Perl before compiling INN.  For instructions on obtaining and installing
@@ -102,7 +102,7 @@
     # cd /usr/include
     # h2ph * sys/*
 
-An even better approach is to install Perl 5.6.1 or later, which have a
+An even better approach is to install S<Perl 5.6.1> or later, which have a
 fixed version of Sys::Syslog that doesn't require this (as well as many
 other improvements over earlier versions of Perl).
 
@@ -264,7 +264,7 @@
 where PREFIX is F</usr/local/news> unless overridden with the option
 above.  The F<history> and F<active> files will be stored in this directory, and
 writes to those files are an appreciable percentage of INN's disk
-activity.  The F<history> file can also be quite large (requiring up to 2 GB
+activity.  The F<history> file can also be quite large (requiring up to S<2 GB>
 or more during nightly B<expire>), so this is a common portion of INN to move
 to a different file system.
 
@@ -296,8 +296,8 @@
 databases (making it difficult to upgrade an earlier INN installation) and
 can significantly increase the size of some of the history database files.
 Large file support is not necessary unless your F<history> database is so
-large that it exceeds 2 GB or you want to use CNFS buffers larger than 2
-GB.
+large that it exceeds S<2 GB> or you want to use CNFS buffers larger than
+S<2 GB>.
 
 The history, tradindexed and buffindexed overview, CNFS, and timecaf
 databases written by an INN built with this option are incompatible with
@@ -307,7 +307,7 @@
 
 Use tagged hash table for the F<history> database.  The tagged hash format
 uses much less memory but is somewhat slower.  This option is recommended
-if you have less than 256 MB of RAM on your news server.  If you install
+if you have less than S<256 MB> of RAM on your news server.  If you install
 INN without tagged hash (the default) and B<expire> takes an excessive amount
 of time, you should make sure the RAM in your system satisfies the
 following formula:
@@ -334,11 +334,11 @@
 =item B<--with-python>
 
 Enables support for Python, allowing you to install filter and
-authentication scripts written in Python.  You will need Python 1.5.2 or
+authentication scripts written in Python.  You will need S<Python 1.5.2> or
 later installed on your system to enable this option.  See
 F<doc/hook-python> for all the details.  Note that there is an
-incompatibility between INN and Python 2.0 when Python is compiled with
-cycle garbage collection; this problem was reported fixed in Python 2.1a1.
+incompatibility between INN and S<Python 2.0> when Python is compiled with
+cycle garbage collection; this problem was reported fixed in S<Python 2.1a1>.
 
 =item B<--with-innd-port>=PORT
 
@@ -386,9 +386,9 @@
 
 If this option is given to configure, B<rnews> will be installed setuid C<news>,
 owned by group C<uucp>, and mode C<4550>.  This will allow the UUCP subsystem
-to run B<rnews> to process UUCP batches of news articles.  Prior to INN 2.3,
+to run B<rnews> to process UUCP batches of news articles.  Prior to S<INN 2.3>,
 installing B<rnews> setuid C<news> was standard; since most sites no longer use
-UUCP, it is no longer the default as of INN 2.3 and must be requested at
+UUCP, it is no longer the default as of S<INN 2.3> and must be requested at
 configure time.  You probably don't want to use this option unless your
 server accepts UUCP news batches.
 
@@ -402,28 +402,28 @@
 even if you have regular login accounts on your news server, INN's B<inews>
 can post fine via a network connection to your running news server and
 doesn't need to use the local socket (which is what setgid enables it to
-do).  Installing B<inews> setgid was the default prior to INN 2.3.
+do).  Installing B<inews> setgid was the default prior to S<INN 2.3>.
 
-=item B<--with-berkeleydb=PATH>
+=item B<--with-berkeleydb>=PATH
 
-Enables support for Berkeley DB (2.x through 4.2.x), which means that it will
+Enables support for S<Berkeley DB> (2.x through 4.2.x), which means that it will
 then be possible to use the ovdb overview method if you wish.  Enabling
 this configure option doesn't mean you'll be required to use ovdb, but it
-does require that Berkeley DB be installed on your system (including the
+does require that S<Berkeley DB> be installed on your system (including the
 header files, not just the runtime libraries).  If a path is given, it
-sets the installed directory of Berkeley DB (configure will search for it
+sets the installed directory of S<Berkeley DB> (configure will search for it
 in some standard locations, but if you have it installed elsewhere, you
 may need this option).
 
-=item B<--with-zlib=PATH>
+=item B<--with-zlib>=PATH
 
 The ovdb storage method can optionally use compression.  If B<--with-berkeleydb>
-is set, and configure finds a suitable Berkeley DB version, this option
+is set, and configure finds a suitable S<Berkeley DB> version, this option
 defaults to C<yes>, otherwise the default is C<no>.  If you have B<zlib> but it is
 not installed under F</usr> or F</usr/local>, you must specify the directory
 where it is installed.
 
-=item B<--with-openssl=PATH>
+=item B<--with-openssl>=PATH
 
 Enables support for SSL for news reading, which means it will be possible
 to have SSL or TLS encrypted NNTP connections between your server and
@@ -601,14 +601,14 @@
 
 It can keep up with a large feed more easily, since it uses large buffers
 to store all overview information, but it's somewhat slower for readers
-(although not as slow as the unified overview in INN 2.2).  You will need
+(although not as slow as the unified overview in S<INN 2.2>).  You will need
 to create the buffers for it to use (very similar to creating CNFS buffers)
 and list the available buffers in F<buffindexed.conf>.  See
 buffindexed.conf(5) for more information.
 
 =item ovdb
 
-It stores overview data in a Berkeley DB database; it's fast and very robust,
+It stores overview data in a S<Berkeley DB> database; it's fast and very robust,
 but may require more disk space.  See the ovdb(5) man page for more
 information on it.
 
@@ -618,7 +618,7 @@
 
 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
+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.
 
@@ -654,7 +654,7 @@
 that matches the group name is used.  Patterns beginning with C<!> mean to
 exclude groups matching that pattern.  For example:
 
-    *, !comp.*, comp.os.*
+    *,!comp.*,comp.os.*
 
 In this case, we're saying we match everything (C<*>), except that we
 don't match anything under comp (C<!comp.*>), unless it is actually under
@@ -710,7 +710,7 @@
 
 If set to true then INN will support the NEWNEWS command for news readers.
 While this can be an expensive operation, its speed has been improved
-considerably as of INN 2.3 and it's probably safe to turn on without
+considerably as of S<INN 2.3> and it's probably safe to turn on without
 risking excessive server load.  The default is true.  (Note that the
 I<access> setting in F<readers.conf> overrides this value; see
 readers.conf(5) for more details.)
@@ -932,8 +932,8 @@
         :Tm:imapfeed!
 
 For more information on B<imapfeed>, look at the
-F<innfeed/imap_connection.c>.  For more information on IMAP in general,
-see RFC 2060.
+F<innfeed/imap_connection.c> file.  For more information on IMAP in general,
+see S<RFC 2060>.
 
 Finally, there is a special entry for controlchan(8), which processes
 newsgroup control messages, that should always be in F<newsfeeds> unless
@@ -1029,7 +1029,7 @@
 Use a block device directly.  This will probably give you the most speed
 since it avoids the file system overhead of large files, but it requires
 your OS support mmap(2) on a block device.  Solaris supports this, as do
-late Linux 2.4 kernels.  FreeBSD does not at last report.  Also on many
+late S<Linux 2.4> kernels.  FreeBSD does not at last report.  Also on many
 PC-based Unixes it is difficult to create more than eight partitions,
 which may limit your options.
 
@@ -1040,7 +1040,7 @@
 
 =back
 
-If you're having doubts, use option #2; it's easier to set up and should
+If you're having doubts, use S<option #2>; it's easier to set up and should
 work regardless of your operating system.  More information about the
 creation of these cycbuffs can be found in cycbuff.conf(5) man page.
 
@@ -1056,19 +1056,19 @@
 
 For each metacycbuff, you now need to determine how many cycbuffs will
 make up the metacycbuff, the size of those cycbuffs, and where they will
-be stored.  Some OSes do not support files larger than 2 GB, which will
+be stored.  Some OSes do not support files larger than S<2 GB>, which will
 limit the size you can make a single cycbuff, but you can still combine
 many cycbuffs into each metacycbuff.  Older versions of Linux are known to
 have this limitation; FreeBSD does not.  Some OSes that support large
 files don't support direct access to block devices for large partitions
-(Solaris prior to Solaris 7, or not running in 64-bit mode, is in this
-category); on those OSes, if you want cycbuffs over 2 GB, you'll have to
-use regular files.  If in doubt, keep your cycbuffs smaller than 2 GB.
+(Solaris prior to S<Solaris 7>, or not running in 64-bit mode, is in this
+category); on those OSes, if you want cycbuffs over S<2 GB>, you'll have to
+use regular files.  If in doubt, keep your cycbuffs smaller than S<2 GB>.
 Also, when laying out your cycbuffs, you will want to try to arrange them
 across as many physical disks as possible (or use a striped disk array and
 put them all on that).
 
-In order to use any cycbuff larger than 2 GB, you need to build INN with
+In order to use any cycbuff larger than S<2 GB>, you need to build INN with
 the B<--enable-largefiles> option.  See L<Installing INN> for more
 information and some caveats.
 
@@ -1081,7 +1081,7 @@
 simple like C<BUFF00>, C<BUFF01>, etc. is a decent choice, or you may want
 to use something that includes the SCSI target and slice number of the
 partition.  SIZE is the buffer size in kilobytes (if you're trying to stay
-under 2 GB, keep your sizes below C<2097152>).
+under S<2 GB>, keep your sizes below C<2097152>).
 
 Now, you need to tell INN how to group your cycbuffs into metacycbuffs.
 This is similar to creating cycbuff entries:
@@ -1307,7 +1307,7 @@
 
     awk -F: \
     '/^cy/ { printf "dd if=/dev/zero of=%s bs=1k count=%s\n", $3, $4 }' \
-    ~news/etc/cycbuff.conf
+    /usr/local/news/etc/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
@@ -1460,7 +1460,7 @@
 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 '/usr/local/news/bin/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>.
@@ -1492,7 +1492,7 @@
 
 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 * * * /usr/local/news/bin/ctlinnd -t 120 -s reload incoming.conf 'flush cache'
 
 
 =head1 File Descriptor Limits

Modified: doc/pod/libinnhist.pod
===================================================================
--- doc/pod/libinnhist.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/libinnhist.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -297,6 +297,6 @@
 
 =head1 HISTORY
 
-Written by Alex Kiernan <alexk at demon.net> for InterNetNews 2.4.0.
+Written by Alex Kiernan <alexk at demon.net> for S<InterNetNews 2.4.0>.
 
 $Id$

Modified: doc/pod/list.pod
===================================================================
--- doc/pod/list.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/list.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -78,6 +78,6 @@
 
 =head1 HISTORY
 
-Written by Alex Kiernan <alex.kiernan at thus.net> for InterNetNews 2.4.0.
+Written by Alex Kiernan <alex.kiernan at thus.net> for S<InterNetNews 2.4.0>.
 
 $Id$

Modified: doc/pod/news.pod
===================================================================
--- doc/pod/news.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/news.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -28,8 +28,8 @@
 
 =item *
 
-INN now uses Autoconf 2.59 or later for configuration.  As a result, some
-configure options have changed slightly and more of the standard --*dir
+INN now uses S<autoconf 2.59> or later for configuration.  As a result, some
+configure options have changed slightly and more of the standard B<--*dir>
 options should be supported in lieu of the old INN-specific options.  See
 C<configure --help> for the available options.
 
@@ -246,7 +246,7 @@
 =item *
 
 configure now looks for sendmail only in /usr/sbin and /usr/lib, not on
-the user's path.  This should reduce the need for --with-sendmail if your
+the user's path.  This should reduce the need for B<--with-sendmail> if your
 preferred sendmail is in a standard location.
 
 =item *
@@ -285,10 +285,10 @@
 
 =head1 Upgrading from 2.3 to 2.4
 
-The inn.conf parser has changed between INN 2.3 and 2.4.  Due to that
+The inn.conf parser has changed between S<INN 2.3> and 2.4.  Due to that
 change, options in F<inn.conf> that contain whitespace or a few other
 special characters must be quoted with double quotes, and empty parameters
-(parameters with no value) are not allowed.  INN 2.4 comes with a script,
+(parameters with no value) are not allowed.  S<INN 2.4> comes with a script,
 B<innupgrade>, run automatically during C<make update>, that will attempt
 to fix any problems that it finds with your F<inn.conf> file, saving the
 original as F<inn.conf.OLD>.
@@ -309,7 +309,7 @@
 shuts down (or fails to shut down) the overview databases.  If you have
 stability problems with ovdb, try setting readserver to true in
 F<ovdb.conf>.  This will funnel all ovdb reads through a single process
-with a cleaner interface to the underlying BerkeleyDB database.
+with a cleaner interface to the underlying S<Berkeley DB> database.
 
 If you use Perl authentication for nnrpd (if I<nnrpdperlauth> in
 F<inn.conf> is true), there have been major changes.  See "Changes to
@@ -330,7 +330,7 @@
 since it now supports UTF-8.  This may require changes in other software
 packages that link against INN's libraries.
 
-If you are upgrading from a version prior to INN 2.3, see L<"Upgrading
+If you are upgrading from a version prior to S<INN 2.3>, see L<"Upgrading
 from 2.2 to 2.3">.
 
 =head1 Changes in 2.4.0
@@ -340,7 +340,7 @@
 =item *
 
 IPv6 support has been added, disabled by default.  If you have IPv6
-connectivity, build with --enable-ipv6 to try it.  There are no known
+connectivity, build with B<--enable-ipv6> to try it.  There are no known
 bugs, but please report any problems you find (or even successes, if you
 use an unusual platform).  There are a few changes of interest; further
 information is available in F<doc/IPv6-info>.
@@ -377,7 +377,7 @@
 
 =item *
 
-nnrpd no longer handles the poorly-specified RFC 977 optional fourth
+nnrpd no longer handles the poorly-specified S<RFC 977> optional fourth
 argument to the NEWGROUPS command specifying the "distributions" that the
 command was supposed to apply to.
 
@@ -443,8 +443,8 @@
 
 =item *
 
-Two configure options have changed names:  --with-tmp-path is now
---with-tmp-dir, and --with-largefiles is now --enable-largefiles, to
+Two configure options have changed names:  B<--with-tmp-path> is now
+B<--with-tmp-dir>, and B<--with-largefiles> is now B<--enable-largefiles>, to
 improve consistency and better match the autoconf option guidelines.
 
 =item *
@@ -467,7 +467,7 @@
 On the writer server configure nfswriter to true and on all of the readers
 configure nfsreader to true; these options add calls to force data out to
 the NFS server and force it to be read directly from the NFS server at the
-appropriate moments.  Note that it has only been tested on Solaris 8,
+appropriate moments.  Note that it has only been tested on S<Solaris 8>,
 using CNFS as the storage mechanism and tradindexed as the overview
 method.
 
@@ -568,7 +568,7 @@
 
 =item *
 
-Compilation fixes with Perl 5.8.0, BerkeleyDB 4.x, current versions of
+Compilation fixes with S<Perl 5.8.0>, S<Berkeley DB 4.x>, current versions of
 Linux (including with large file support), and Tru64.  inndf fixes for
 ReiserFS.
 
@@ -660,7 +660,7 @@
 
 =item *
 
-A very long-standing (since INN 1.0!) NNTP protocol bug in nnrpd was
+A very long-standing (since S<INN 1.0>!) NNTP protocol bug in nnrpd was
 fixed.  The response to an ARTICLE command retrieving a message by message
 ID should have the message ID as the third word of the response, not the
 fourth.  Fixing this is reported to *possibly* cause problems with some
@@ -729,7 +729,7 @@
 of both files have changed between 2.2 and 2.3.  Regardless of whether you
 were using the storage API or traditional spool under 2.2, you'll need to
 rebuild your overview and history files.  You will also need to add a
-storage.conf file, if you weren't using the storage API under INN 2.2.  A
+storage.conf file, if you weren't using the storage API under S<INN 2.2>.  A
 good default storage.conf file for 2.2 users would be:
 
     method tradspool {
@@ -825,8 +825,8 @@
 
     $lines = $hdr{'__LINES__'};
 
-to work with INN 2.3 or later.  This is due to an internal optimization of
-the interface to embedded filters that's new in INN 2.3.
+to work with S<INN 2.3> or later.  This is due to an internal optimization of
+the interface to embedded filters that's new in S<INN 2.3>.
 
 =head1 Changes in 2.3.0
 
@@ -845,8 +845,8 @@
 is very like traditional overview but uses an additional index file.  The
 second (buffindexed) uses large buffers rather than separate files for
 each group and can handle a higher incoming article rate while still being
-fast for readers.  The third (ovdb) uses Berkeley DB to store overview
-information (so you need to have Berkeley DB installed to use it).  The
+fast for readers.  The third (ovdb) uses S<Berkeley DB> to store overview
+information (so you need to have S<Berkeley DB> installed to use it).  The
 I<ovmethod> key in F<inn.conf> chooses the overview method to use.
 
 Note that ovdb has not been as widely tested as the other overview
@@ -922,7 +922,7 @@
 
 =item *
 
-Embedded Perl filters now work with Perl 5.6.0.
+Embedded Perl filters now work with S<Perl 5.6.0>.
 
 =item *
 

Modified: doc/pod/newsfeeds.pod
===================================================================
--- doc/pod/newsfeeds.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/newsfeeds.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -355,7 +355,7 @@
 there are more file feeds than allowed by the system, they will be
 buffered internally in least-recently-used order.  If the internal buffer
 grows bigger then I<size> bytes, however, the data will be written out to
-the appropriate file.  The default value is 16 KB.
+the appropriate file.  The default value is S<C<16> KB>.
 
 =item B<N> I<status>
 

Modified: doc/pod/newsgroups.pod
===================================================================
--- doc/pod/newsgroups.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/newsgroups.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -66,7 +66,6 @@
 Here is an example of moderated newsgroup:
 
     news.lists.misc	News-related statistics and lists. (Moderated)
-    news.admin.announce	Announcements for news adminstrators. (Moderated)
 
 Traditionally, all newsgroup descriptions ended with a period, but this
 is not necessary and steals away one character that is occasionally
@@ -109,6 +108,9 @@
     control.rmgroup	Newsgroup removal control messages (no posting).
     junk		Unfiled articles (no posting).
 
+These lines I<must> be tab-delimited, so please be careful in case you copy
+and paste them from above.
+
 =head1 HISTORY
 
 Written by Julien Elie <julien at trigofacile.com> for InterNetNews.

Modified: doc/pod/newslog.pod
===================================================================
--- doc/pod/newslog.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/newslog.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -6,7 +6,7 @@
 
 Most log files created by Usenet programs reside in the I<pathlog> directory
 set in F<inn.conf> and have a C<.log> extension.  Several versions are usually
-kept with an additional extension such as C<.1>, C<.2>, etc. -- the higher
+kept with an additional extension such as C<.1>, C<.2>, etc. S<-- the> higher
 the number, the older the log.  These old versions are stored in I<pathlog>/OLD;
 they may be compressed and thus may have a C<.1.gz>, C<.2.gz>, etc. extension,
 up to C<.nn.gz> where C<nn> is the number of old logs kept by B<scanlogs>
@@ -144,7 +144,8 @@
 
     news.crit		<pathlog>/news.crit
 
-(A typical entry is shown; it should agree with I<pathlog> in F<inn.conf>.)
+(A typical entry is shown; it should agree with I<pathlog> in F<inn.conf>
+and be tab-delimited.)
 
 =item F<news.err>
 
@@ -160,7 +161,8 @@
 
     news.err		<pathlog>/news.err
 
-(A typical entry is shown; it should agree with I<pathlog> in F<inn.conf>.)
+(A typical entry is shown; it should agree with I<pathlog> in F<inn.conf>
+and be tab-delimited.)
 
 =item F<news.notice>
 
@@ -174,7 +176,8 @@
 
     news.notice		<pathlog>/news.notice
 
-(A typical entry is shown; it should agree with I<pathlog> in F<inn.conf>.)
+(A typical entry is shown; it should agree with I<pathlog> in F<inn.conf>
+and be tab-delimited.)
 
 =item F<nntpsend.log>
 

Modified: doc/pod/nnrpd.pod
===================================================================
--- doc/pod/nnrpd.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/nnrpd.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -146,7 +146,7 @@
 =item B<-S>
 
 If specified, B<nnrpd> will start a negotiation for SSL session as
-soon as connected. To use this flag, C<--with-openssl> must have been
+soon as connected. To use this flag, B<--with-openssl> must have been
 specified at C<configure> time.  For more information on running B<nnrpd>
 with SSL support, see L<SSL SUPPORT>.
 
@@ -161,7 +161,7 @@
 
 =head1 SSL SUPPORT
 
-If INN is built with C<--with-openssl>, B<nnrpd> will support news reading
+If INN is built with B<--with-openssl>, B<nnrpd> will support news reading
 over TLS (also known as SSL).  For clients that use the STARTTLS command,
 no special configuration is needed beyond creating a TLS/SSL certificate
 for the server.  You should do this in exactly the same way that you would
@@ -203,7 +203,7 @@
 
 =head1 PROTOCOL DIFFERENCES
 
-B<nnrpd> implements the NNTP commands defined in RFC 977, with the
+B<nnrpd> implements the NNTP commands defined in S<RFC 977>, with the
 following differences:
 
 =over 4
@@ -230,14 +230,14 @@
 
 The C<xhdr>, C<authinfo user> and C<authinfo pass> commands are
 implemented.  These are based on the reference Unix implementation.  See
-RFC 2980.
+S<RFC 2980>.
 
 =item 4.
 
 A new command, C<xpat header range|MessageID pat [morepat...]>, is
 provided.  The first argument is the case-insensitive name of the header
 to be searched.  The second argument is either an article range or a
-single Message-ID, as specified in RFC 977.  The third argument is a
+single Message-ID, as specified in S<RFC 977>.  The third argument is a
 C<uwildmat>(3)-style pattern; if there are additional arguments they are
 joined together separated by a single space to form the complete pattern.
 This command is similar to the C<xhdr> command.  It returns a C<221>

Modified: doc/pod/ovdb.pod
===================================================================
--- doc/pod/ovdb.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/ovdb.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -4,47 +4,47 @@
 
 =head1 DESCRIPTION
 
-Ovdb is a storage method that uses the BerkeleyDB library to store
-overview data.  It requires version 2.6.x or later of the BerkeleyDB
+Ovdb is a storage method that uses the S<Berkeley DB> library to store
+overview data.  It requires version 2.6.x or later of the S<Berkeley DB>
 library, but has mostly been tested with version 3 and 4.
 
 Ovdb makes use of the full transaction/logging/locking functionality of
-the BerkeleyDB environment.  BerkeleyDB may be downloaded from
+the S<Berkeley DB> environment.  S<Berkeley DB> may be downloaded from
 L<http://www.sleepycat.com> and is needed to build the ovdb backend.
 
 =head1 UPGRADING
 
 This is version 2 of ovdb.  If you have a database created with a previous
-version of ovdb (such as the one shipped with INN 2.3.0) your database
+version of ovdb (such as the one shipped with S<INN 2.3.0>) your database
 will need to be upgraded using ovdb_init(8).  See the man page
 ovdb_init(8) for upgrade instructions.
 
 =head1 INSTALLATION
 
-To build ovdb support into INN, specify the option C<--with-berkeleydb>
+To build ovdb support into INN, specify the option B<--with-berkeleydb>
 when running the configure script.  By default, configure will search for
-a BerkeleyDB tree in several likely locations, and choose the highest
+a S<Berkeley DB> tree in several likely locations, and choose the highest
 version (based on the name of the directory, e.g., F<BerkeleyDB.3.0>) that
 it finds.  There will be a message in the configure output indicating the
 chosen pathname.
 
 You can override this pathname by adding a path to the option, e.g.,
-C<--with-berkeleydb=/usr/BerkeleyDB.3.1>.  This directory is expected to
+B<--with-berkeleydb=/usr/BerkeleyDB.3.1>.  This directory is expected to
 have subdirectories F<include> and F<lib>, containing F<db.h>, and the
 library itself, respectively.
 
 The ovdb database may take up more disk space for a given spool than the
-other overview methods.  Plan on needing at least 1.1 KB for every article
+other overview methods.  Plan on needing at least S<1.1 KB> for every article
 in your spool (not counting crossposts).  So, if you have 5 million
-articles, you'll need at least 5.5 GB of disk space for ovdb. With compression
-enabled, this estimate changes to 0.7 KB per article.  See the L<COMPRESSION>
+articles, you'll need at least S<5.5 GB> of disk space for ovdb. With compression
+enabled, this estimate changes to S<0.7 KB> per article.  See the L<COMPRESSION>
 section below.
-With BerkeleyDB 2.x, the db files are 'grow only'; the library will not shrink
+With S<Berkeley DB 2.x>, the db files are 'grow only'; the library will not shrink
 them, even if data is removed.  So, reserving extra space above the
 estimate is a good idea.  Plus, you'll need additional space for
-transaction logs: at least 100 MB.  By default the transaction logs go in
+transaction logs: at least S<100 MB>.  By default the transaction logs go in
 the same directory as the database.  To improve performance, they can be
-placed on a different disk -- see the L<DB_CONFIG> section.
+placed on a different disk S<-- see> the L<DB_CONFIG> section.
 
 =head1 CONFIGURATION
 
@@ -88,25 +88,25 @@
 
 =item txn_nosync
 
-If txn_nosync is set to false, BerkeleyDB flushes the log after every
+If txn_nosync is set to false, S<Berkeley DB> flushes the log after every
 transaction.  This minimizes the number of transactions that may be lost
 in the event of a crash, but results in significantly degraded
 performance.  Default is true.
 
 =item useshm
 
-If useshm is set to true, BerkeleyDB will use shared memory instead of
+If useshm is set to true, S<Berkeley DB> will use shared memory instead of
 mmap for its environment regions (cache, lock, etc).  With some platforms,
 this may improve performance.  Default is false.  This parameter is
-ignored if you have BerkeleyDB 2.x
+ignored if you have S<Berkeley DB 2.x>.
 
 =item shmkey
 
-Sets the shared memory key used by BerkeleyDB when 'useshm' is true.
-BerkeleyDB will create several (usually 5) shared memory segments, using
+Sets the shared memory key used by S<Berkeley DB> when 'useshm' is true.
+S<Berkeley DB> will create several (usually 5) shared memory segments, using
 sequentially numbered keys starting with 'shmkey'.  Choose a key that does
 not conflict with any existing shared memory segments on your system.
-Default is 6400.  This parameter is only used with BerkeleyDB 3.1 or
+Default is 6400.  This parameter is only used with S<Berkeley DB 3.1> or
 newer.
 
 =item pagesize
@@ -117,7 +117,7 @@
 
 =item minkey
 
-Sets the minimum number of keys per page.  See the BerkeleyDB
+Sets the minimum number of keys per page.  See the S<Berkeley DB>
 documentation for more info.  Default is based on page size
 and whether compression is enabled:
 
@@ -131,7 +131,7 @@
 
 =item maxlocks
 
-Sets the BerkeleyDB "lk_max" parameter, which is the maxmium number of
+Sets the S<Berkeley DB> "lk_max" parameter, which is the maxmium number of
 locks that can exist in the database at the same time.  Default is 4000.
 
 =item nocompact
@@ -155,13 +155,13 @@
 
 =item readserver
 
-Normally, each nnrpd process directly accesses the BerkeleyDB environment.
+Normally, each nnrpd process directly accesses the S<Berkeley DB> environment.
 The process of attaching to the database (and detaching when finished) is
 fairly expensive, and can result in high loads in situations when there
 are lots of reader connections of relatively short duration.
 
 When the readserver parameter is "true", the nnrpds will access overview
-via a helper server (B<ovdb_server> -- which is started by B<ovdb_init>).
+via a helper server (B<ovdb_server> S<-- which> is started by B<ovdb_init>).
 This can also result in cleaner shutdowns for the database, improving
 stability and avoiding deadlocks and corrupted databases.  If you are
 experiencing any instability in ovdb, try setting this parameter to true.
@@ -234,7 +234,7 @@
 
 Another thing that you can do with this file is to split the overview
 database across multiple disks.  In the F<DB_CONFIG> file, you can list
-directories that BerkeleyDB will search when it goes to open a database.
+directories that S<Berkeley DB> will search when it goes to open a database.
 
 For example, let's say that you have I<pathoverview> set to
 F</mnt/overview> and you have four additional file systems created on
@@ -247,7 +247,7 @@
     set_data_dir /mnt/ov3
     set_data_dir /mnt/ov4
 
-(For BerkeleyDB 2.x, replace C<set_data_dir> with C<DB_DATA_DIR>.)
+(For S<Berkeley DB 2.x>, replace C<set_data_dir> with C<DB_DATA_DIR>.)
 
 Distribute your ovNNNNN files into the four filesystems.  (say, 8 each).
 When called upon to open a database file, the db library will look for it
@@ -258,9 +258,9 @@
 news processes that use the database are shut down first (including
 nnrpds).
 
-The DB_CONFIG functionality is part of BerkeleyDB itself, rather than
-something provided by ovdb.  See the BerkeleyDB documentation for complete
-details for the version of BerkeleyDB that you're running.
+The DB_CONFIG functionality is part of S<Berkeley DB> itself, rather than
+something provided by ovdb.  See the S<Berkeley DB> documentation for complete
+details for the version of S<Berkeley DB> that you're running.
 
 =head1 RUNNING
 
@@ -323,7 +323,7 @@
 
 =item I<pathoverview>
 
-Directory where the database goes.  BerkeleyDB calls it the 'DB_HOME'
+Directory where the database goes.  S<Berkeley DB> calls it the 'DB_HOME'
 directory.
 
 =item I<pathoverview>/DB_CONFIG
@@ -357,7 +357,7 @@
 inn.conf(5), innd(8), nnrpd(8), ovdb_init(8), ovdb_monitor(8),
 ovdb_stat(8)
 
-BerkeleyDB documentation: in the F<docs> directory of the BerkeleyDB
+S<Berkeley DB> documentation: in the F<docs> directory of the S<Berkeley DB>
 source distribution, or on the Sleepycat web page:
 L<http://www.sleepycat.com/>.
 

Modified: doc/pod/ovdb_init.pod
===================================================================
--- doc/pod/ovdb_init.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/ovdb_init.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -76,8 +76,8 @@
 
 =item *
 
-You upgrade the BerkeleyDB library to a newer version, for example
-from 2.7.7 to 3.1.17.  In this case, the BerkeleyDB db->upgrade()
+You upgrade the S<Berkeley DB> library to a newer version, for example
+from 2.7.7 to 3.1.17.  In this case, the S<Berkeley DB> db->upgrade()
 method is used.
 
 =item *
@@ -92,19 +92,19 @@
 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 BerkeleyDB
-2.7.7 to use BerkeleyDB 3.1.17:
+Here's an example procedure to upgrade a database created with
+S<Berkeley DB 2.7.7> to use S<Berkeley DB 3.1.17>:
 
 =over 4
 
 =item 1
 
-Build and install the BerkeleyDB 3.1.17
+Build and install the S<Berkeley DB 3.1.17>
 
 =item 2
 
 Run configure in the INN source tree and make sure it picks up the
-right BerkeleyDB directory (e.g., /usr/local/BerkeleyDB.3.1)
+right S<Berkeley DB> directory (e.g., /usr/local/BerkeleyDB.3.1)
 
 =item 3
 

Modified: doc/pod/ovdb_stat.pod
===================================================================
--- doc/pod/ovdb_stat.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/ovdb_stat.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -10,7 +10,7 @@
 
 =head1 DESCRIPTION
 
-B<ovdb_stat> displays information from the ovdb database: BerkeleyDB
+B<ovdb_stat> displays information from the ovdb database:  S<Berkeley DB>
 statistics, newsgroup data, and overview records; and optionally
 outputs in HTML format.
 
@@ -44,18 +44,18 @@
 
 =item B<-k>
 
-Displays lock region statistics, as returned by the BerkeleyDB lock_stat()
+Displays lock region statistics, as returned by the S<Berkeley DB> lock_stat()
 call.
 
 =item B<-l>
 
-Displays log region statistics, as returned by the BerkeleyDB log_stat()
+Displays log region statistics, as returned by the S<Berkeley DB> log_stat()
 call.
 
 =item B<-m>
 
 Displays global memory pool statistics, as returned by the
-BerkeleyDB memp_stat() call.
+S<Berkeley DB> memp_stat() call.
 
 =item B<-M>
 
@@ -64,17 +64,17 @@
 
 =item B<-t>
 
-Displays log region statistics, as returned by the BerkeleyDB txn_stat()
+Displays log region statistics, as returned by the S<Berkeley DB> txn_stat()
 call.
 
 =item B<-v>
 
-Displays ovdb version, and BerkeleyDB version.
+Displays ovdb version, and S<Berkeley DB> version.
 
 =item B<-d> I<database>
 
 Displays information about the given database, as returned by the
-BerkeleyDB db->stat() call.  This operation may take a long time
+S<Berkeley DB> db->stat() call.  This operation may take a long time
 on busy systems (several minutes or more).
 
 =back

Modified: doc/pod/passwd.nntp.pod
===================================================================
--- doc/pod/passwd.nntp.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/passwd.nntp.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -27,7 +27,7 @@
 At present, the only recognized "authentication style" is C<authinfo>;
 this is also the default.  It means that NNTP "authinfo" commands are
 used to authenticate to the remote host.  (The C<authinfo> command is a
-common extension to RFC 977.)
+common extension to S<RFC 977>.)
 
 For example:
 

Modified: doc/pod/qio.pod
===================================================================
--- doc/pod/qio.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/qio.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -42,7 +42,7 @@
 B<QIOopen> opens the given file for reading.  For regular files, if your
 system provides that information and the size is reasonable, QIO will use
 the block size of the underlying file system as its buffer size;
-otherwise, it will default to a buffer of 8 KB.  Returns a pointer to use
+otherwise, it will default to a buffer of S<8 KB>.  Returns a pointer to use
 for subsequent calls, or NULL on error.  B<QIOfdopen> performs the same
 operation except on an already-open file descriptor (I<fd> must designate
 a file open for reading).

Modified: doc/pod/radius.pod
===================================================================
--- doc/pod/radius.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/radius.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -72,6 +72,6 @@
 
 nnrpd(8), radius.conf(5), readers.conf(5)
 
-RFC 2865, Remote Authentication Dial In User Service.
+S<RFC 2865>, Remote Authentication Dial In User Service.
 
 =cut

Modified: doc/pod/readme.pod
===================================================================
--- doc/pod/readme.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/readme.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -1,6 +1,6 @@
-=head1 Welcome to INN 2.5!
+=head1 Welcome to S<INN 2.5>!
 
-This is the current development version of INN 2.5.  This code is under
+This is the current development version of S<INN 2.5>.  This code is under
 active development and may or may not be stable at any given time.
 Contributions and bug reports are welcome and encouraged.
 
@@ -14,8 +14,8 @@
 
 INN (InterNetNews), originally written by Rich Salz, is an extremely
 flexible and configurable Usenet / netnews news server.  For a complete
-description of the protocols behind Usenet and netnews, see RFC 1036 and
-RFC 977 (or their replacements).  In brief, netnews is a set of protocols
+description of the protocols behind Usenet and netnews, see S<RFC 1036> and
+S<RFC 977> (or their replacements).  In brief, netnews is a set of protocols
 for exchanging messages between a decentralized network of news servers.
 News articles are organized into newsgroups, which are themselves
 organized into hierarchies.  Each individual news server stores locally
@@ -69,8 +69,8 @@
 
 =head1 Prerequisites
 
-Compiling INN requires an ANSI C compiler (gcc is recommended).  INN was
-originally written in K&R C, but supporting pre-ANSI compilers has become
+Compiling INN requires an S<ANSI C> compiler (gcc is recommended).  INN was
+originally written in S<K&R C>, but supporting pre-ANSI compilers has become
 enough of a headache that a lot of the newer parts of INN will no longer
 compile with a non-ANSI compiler.  gcc itself will compile with most
 vendor non-ANSI compilers, however, so if you're stuck with one,
@@ -88,11 +88,11 @@
 successfully run INN on a platform that isn't listed in F<INSTALL>, please
 let us know (see L<"Reporting Bugs"> below).
 
-Perl 5.003 or later is required to build INN.  Perl 5.004 is required if
+S<Perl 5.003> or later is required to build INN.  S<Perl 5.004> is required if
 you want the embedded Perl filter support (which is highly recommended;
 some excellent spam filters have been written for INN).  Since all
 versions of Perl previous to 5.004 are buggy (including security problems)
-and have fewer features, installing Perl 5.004 or later is recommended.
+and have fewer features, installing S<Perl 5.004> or later is recommended.
 
 If you want to enable PGP verification of control messages (highly
 recommended), you will need to have a PGP implementation installed.  See
@@ -104,7 +104,7 @@
 because of the wide variety of pieces that have to be configured (who is
 authorized to read from the server, what newsgroups it carries, and how
 the articles are stored on disk at a bare minimum, and if the server isn't
-completely stand-alone -- and very few servers are -- both incoming and
+completely stand-alone S<-- and> very few servers S<are --> both incoming and
 outgoing feeds have to be set up and tested).  Be prepared to take some
 time to understand what's going on and how all the pieces fit together.
 If you have any specific suggestions for documentation, or comments about

Modified: doc/pod/simpleftp.pod
===================================================================
--- doc/pod/simpleftp.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/simpleftp.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -24,7 +24,7 @@
 administrators to install yet another package.  Its shortcomings as a
 general purpose program are too numerous to mention, but one that stands
 out is that B<simpleftp> does not understand the complete syntax of URLs,
-only the hostname and pathname parts -- it will not understand username,
+only the hostname and pathname parts S<-- it> will not understand username,
 password, port or parameter strings.
 
 The Perl libraries that it uses have the advantage of coming with Perl,

Modified: doc/pod/storage.conf.pod
===================================================================
--- doc/pod/storage.conf.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/storage.conf.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -58,7 +58,7 @@
 
 =over 4
 
-=item B<class>
+=item I<class>: <storage_class>
 
 An identifier for this storage method entry.  <storage_class> should be
 a number between 0 and 255.  It should be unique across all of the entries in
@@ -69,7 +69,7 @@
 permanent (since it is used in storage tokens).  Storage classes can be
 for instance numbered sequentially in F<storage.conf>.
 
-=item B<newsgroups>
+=item I<newsgroups>: <wildmat>
 
 What newsgroups are stored using this storage method.  <wildmat> is a uwildmat(3)
 pattern which is matched against the newsgroups an article is posted to.
@@ -84,7 +84,7 @@
 There is no default newsgroups pattern; if an entry should match all
 newsgroups, use an explicit C<newsgroups: *>.
 
-=item B<size>
+=item I<size>: <minsize>[,<maxsize>]
 
 A range of article sizes (in bytes) which should be stored using this storage
 method.  If <maxsize> is C<0> or not given, the upper size of articles is
@@ -94,7 +94,7 @@
 requirements of this storage method entry).  By default, <minsize> is set
 to C<0>.
 
-=item B<expires>
+=item I<expires>: <mintime>[,<maxtime>]
 
 A range of article expiration times which should be stored using this storage
 method.  Be careful; this is less useful than it may appear at first.  This
@@ -118,13 +118,13 @@
 A <mintime> value greater than C<0s> implies that this storage method won't
 match any article without an Expires: header.
 
-=item B<options>
+=item I<options>: <options>
 
 This key is for passing special options to storage methods that require them
 (currently only C<cnfs>).  See the L<STORAGE METHODS> section below for
 a description of its use.
 
-=item B<exactmatch>
+=item I<exactmatch>: <bool>
 
 If this key is set to true, all the newsgroups in the Newsgroups: header of
 incoming articles will be examined to see if they match newsgroups patterns.
@@ -283,7 +283,7 @@
 
 The following sample F<storage.conf> file would store all articles
 posted to alt.binaries.* in the C<BINARIES> CNFS metacycbuff,
-all articles over roughly 50 KB in any other hierarchy in the C<LARGE> CNFS
+all articles over roughly S<50 KB> in any other hierarchy in the C<LARGE> CNFS
 metacycbuff, all other articles in alt.* in one timehash class, and all
 other articles in any newsgroups in a second timehash class, except for
 the internal.* hierarchy which is stored in traditional spool format.
@@ -316,7 +316,7 @@
 a good habit to get into; make sure that you have at least one catch-all
 entry just in case something you did not expect falls through the cracks.
 Notice also that the special rule for the internal.* hierarchy is first,
-so it will catch even articles crossposted to alt.binaries.* or over 50 KB
+so it will catch even articles crossposted to alt.binaries.* or over S<50 KB>
 in size.
 
 As for poison wildmat expressions, if you have for instance an article

Modified: doc/pod/tdx-util.pod
===================================================================
--- doc/pod/tdx-util.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/tdx-util.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -161,9 +161,9 @@
 end of each entry will be four additional pieces of data:  the article
 number according to the index file for that group labelled with
 C<Article:>, the storage API token for that article labelled with
-C<Token:>, the arrival date for that article on the server in RFC 822 date
+C<Token:>, the arrival date for that article on the server in S<RFC 822> date
 format labelled with C<Arrived:>, and the expiration date for that article
-(from the Expires header) in RFC 822 date format if there is any, labelled
+(from the Expires header) in S<RFC 822> date format if there is any, labelled
 with C<Expires:>.
 
 If this option is given, the B<-n> option must also be given to specify

Modified: doc/pod/tinyleaf.pod
===================================================================
--- doc/pod/tinyleaf.pod	2007-08-31 18:03:14 UTC (rev 7663)
+++ doc/pod/tinyleaf.pod	2007-09-02 12:58:07 UTC (rev 7664)
@@ -40,7 +40,7 @@
 F</etc/hosts.allow> and F</etc/hosts.deny> to restrict who can talk to the
 server.)
 
-B<tinyleaf> has a (currently hard-coded) maximum message size of 1MB and a
+B<tinyleaf> has a (currently hard-coded) maximum message size of S<1 MB> and a
 (similarly hard-coded) timeout of ten minutes for each command or chunk of
 article data.
 
@@ -59,7 +59,7 @@
     nntp stream tcp nowait archive /usr/sbin/tcpd \
       /usr/local/bin/tinyleaf /var/spool/tinyleaf /usr/local/bin/archive
 
-(all on one line -- the backslash and split in this line is just for
+(all on one line S<-- the> backslash and split in this line is just for
 readability) where C<archive> is the user that owns the archive,
 C</usr/sbin/tcpd> is the path to tcpd(8), C</usr/local/bin/tinyleaf> is
 the path to this program, F</var/spool/tinyleaf> is some scratch directory

Modified: samples/actsync.ign
===================================================================
--- samples/actsync.ign	2007-08-31 18:03:14 UTC (rev 7663)
+++ samples/actsync.ign	2007-09-02 12:58:07 UTC (rev 7664)
@@ -1,8 +1,9 @@
 ##  $Id$
 ##
-##  Sample actsync ignore_file.
+##  Sample actsync ignore file.
 ##
-##  It defines synchronization rules.
+##  It defines synchronization rules (which newsgroups will be
+##  checked and which will be ignored).
 ##  See the actsync man page for more information.
 
 ##  For now by default do not sync.



More information about the inn-committers mailing list