INN commit: trunk/doc/pod (news.pod)

INN Commit Russ_Allbery at isc.org
Thu Apr 3 12:26:56 UTC 2008


    Date: Thursday, April 3, 2008 @ 05:26:55
  Author: iulius
Revision: 7721

Fix some typos and podify the file.
A bug noted in 2.5 was fixed in 2.4.2.

Modified:
  trunk/doc/pod/news.pod

----------+
 news.pod |  317 ++++++++++++++++++++++++++++++-------------------------------
 1 file changed, 156 insertions(+), 161 deletions(-)

Modified: news.pod
===================================================================
--- news.pod	2008-04-03 12:24:31 UTC (rev 7720)
+++ news.pod	2008-04-03 12:26:55 UTC (rev 7721)
@@ -18,61 +18,54 @@
 itself the way that it could before.  If you get error messages about
 resetting the file descriptor limits, you may need to increase the file
 descriptor limits as root before running B<rc.news> as the news user.  See
-the sample init script in contrib for an example of how to do this.  More
-information on file descriptor limits can be found in INSTALL.
+the sample init script in F<contrib> for an example of how to do this.  More
+information on file descriptor limits can be found in F<INSTALL>.
 
 In F<newsfeeds>, B<innfeed> should be run directly rather than through
 B<startinnfeed>.  B<innupgrade> will attempt to take care of this
-modification during make update.  When starting B<innd> by hand, B<innd>
+modification during C<make update>.  When starting B<innd> by hand, B<innd>
 can just be run directly rather than using B<inndstart>.
 
 =item *
 
 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>
+C<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.
 
 =item *
 
-tinyleaf, a miniature IHAVE-only leaf server, is now included.  See the
+B<tinyleaf>, a miniature IHAVE-only leaf server, is now included.  See the
 tinyleaf(8) man page for more information.
 
 =item *
 
-The Perl and Python filter_mode hooks are now called when innd is shutting
+The Perl and Python filter_mode hooks are now called when B<innd> is shutting
 down via either C<ctlinnd shutdown> or C<ctlinnd xexec> with a new mode
-value of "shutdown".  This will allow the Perl hooks to save filter data
-across innd restarts without requiring that the news administrator
+value of C<shutdown>.  This will allow the Perl hooks to save filter data
+across B<innd> restarts without requiring that the news administrator
 throttle the server first.  (Python already had a separate close hook that
 is also called.)
 
 =item *
 
-Support for embedded Tcl filters in innd has been removed.  It hasn't
-worked for some time and causes innd crashes if compiled in (even if not
+Support for embedded Tcl filters in B<innd> has been removed.  It hasn't
+worked for some time and causes B<innd> crashes if compiled in (even if not
 used).  If someone wants to step forward and maintain it, I recommend
 starting from scratch and emulating the Perl and Python filters.
 
 =item *
 
-If a user is not authorized to approve articles (using the A access
-control in readers.conf), articles that include Approved headers will be
-rejected even if posted to unmoderated groups.  Some other site may
-consider that group to be moderated.
-
-=item *
-
-If strippath is set in readers.conf, the whole user-supplied Path header
+If I<strippath> is set in F<readers.conf>, the whole user-supplied Path: header
 will now be stripped.  Previously, the final component of the
-user-supplied Path would still be retained.
+user-supplied Path: would still be retained.
 
 =item *
 
-The -g option to nnrpd is no longer supported.  If you are verifying
+The B<-g> option to B<nnrpd> is no longer supported.  If you are verifying
 passwords against the system password database, see the ckpasswd(8) man
-page, and in particular the -s option.  (A much better idea would be to
-just use PAM, which ckpasswd supports.)
+page, and in particular the B<-s> option.  (A much better idea would be to
+just use PAM, which B<ckpasswd> supports.)
 
 =back
 
@@ -83,15 +76,15 @@
 =item *
 
 Previous versions of INN had an optimization for handling XHDR Newsgroups
-that used the Xref header from overview.  While this does make the command
+that used the Xref: header from overview.  While this does make the command
 much faster, it doesn't produce accurate results and breaks the NNTP
 protocol, so this optimization has been removed.
 
 =item *
 
-Fixed a bug in innd that allowed it to accept articles with duplicated
+Fixed a bug in B<innd> that allowed it to accept articles with duplicated
 headers if the header occurred an odd number of times.  Modified the
-programs for rebuilding overview to use the last Xref header if there
+programs for rebuilding overview to use the last Xref: header if there
 are multiple ones to avoid problems with spools that contain such invalid
 articles.
 
@@ -103,17 +96,17 @@
 =item *
 
 Increase the send and receive buffer on the Unix domain socket used by
-ctlinnd.  This should allow longer replies (particularly for innstat) on
+B<ctlinnd>.  This should allow longer replies (particularly for B<innstat>) on
 platforms with very low default Unix domain socket buffer sizes.
 
 =item *
 
-rnews's handling of articles with nul characters, NNTP errors, header
+B<rnews>'s handling of articles with nul characters, NNTP errors, header
 problems, and deferrals has been significantly improved.
 
 =item *
 
-Thomas Parmelan added support to send-uucp for specifying the funnel or
+Thomas Parmelan added support to B<send-uucp> for specifying the funnel or
 exploder site to flush for feeds managed through one and fixed a problem
 with picking up old stranded work files.
 
@@ -136,9 +129,9 @@
 
 =item *
 
-make install and make update now always install the newly built binaries,
+C<make install> and C<make update> now always install the newly built binaries,
 rather than only installing them if the modification times are newer.
-This is the behavior that people expect.  make install now also
+This is the behavior that people expect.  C<make install> now also
 automatically builds a new (empty) history database if one doesn't already
 exist.
 
@@ -146,19 +139,19 @@
 
 The embedded Tcl filter code has been disabled (and will be removed
 entirely in the next major release of INN).  It hasn't worked for some
-time and causes innd crashes if compiled in (even if not used).  If
+time and causes B<innd> crashes if compiled in (even if not used).  If
 someone wants to step forward and maintain it, I recommend starting from
 scratch and emulating the Perl and Python filters.
 
 =item *
 
-ctlinnd should now successfully handle messages from INN up to the maximum
+B<ctlinnd> should now successfully handle messages from INN up to the maximum
 allowable packet size in the protocol, fixing problems sites with many
-active peers were having with innstat output.
+active peers were having with B<innstat> output.
 
 =item *
 
-Overview generation has been fixed in both makehistory and innd to follow
+Overview generation has been fixed in both B<makehistory> and B<innd> to follow
 the rules in the latest NNTP draft rather than just replacing special
 characters with spaces.  This means that the unfolding of folded header
 lines will not introduce additional, incorrect whitespace in the overview
@@ -166,22 +159,22 @@
 
 =item *
 
-B<nnrpd> now uniformly responds with a 480 or 502 status code to attempts
+B<nnrpd> now uniformly responds with a C<480> or C<502> status code to attempts
 to read a newsgroup to which the user does not have access, depending on
-whether the user has authenticated.  Previously, it returned a 411 status
+whether the user has authenticated.  Previously, it returned a C<411> status
 code, claiming the group didn't exist, which confuses the reactive
 authentication capability of news readers.
 
 =item *
 
-If a user is not authorized to approve articles (using the A access
-control in readers.conf), articles that include Approved headers will be
+If a user is not authorized to approve articles (using the C<A> I<access>
+control in F<readers.conf>), articles that include Approved: headers will be
 rejected even if posted to unmoderated groups.  Some other site may
 consider that group to be moderated.
 
 =item *
 
-The configuration parser used for readers.conf and others now correctly
+The configuration parser used for F<readers.conf> and others now correctly
 handles C<#> inside quoted strings and is more robust against unmatched
 double quotes.
 
@@ -192,17 +185,17 @@
 
 =item *
 
-A bug that could cause heap corruption and random crashes in innd if INN
+A bug that could cause heap corruption and random crashes in B<innd> if INN
 were compiled with Python support has been fixed.
 
 =item *
 
-Some problems with innd's tracking of article size and enforcement of the
+Some problems with B<innd>'s tracking of article size and enforcement of the
 configured maximum article size have been fixed.
 
 =item *
 
-pgpverify will now correctly verify signatures generated by GnuPG and
+B<pgpverify> will now correctly verify signatures generated by GnuPG and
 better supports GnuPG as the PGP implementation.
 
 =item *
@@ -213,8 +206,8 @@
 
 =item *
 
-Improved the error reporting in the history database code, in inews, in
-controlchan, and in expire.
+Improved the error reporting in the history database code, in B<inews>, in
+B<controlchan>, and in B<expire>.
 
 =item *
 
@@ -228,15 +221,15 @@
 
 =item *
 
-SECURITY: Handle the special filing of control messages into per-type
+SECURITY:  Handle the special filing of control messages into per-type
 newsgroups more robustly.  This closes a potentially exploitable buffer
 overflow.  Thanks to Dan Riley for his excellent bug report.
 
 =item *
 
-Fixed article handling in innd so that articles without a Path header
+Fixed article handling in B<innd> so that articles without a Path: header
 (arising from peers sending malformatted articles or injecting
-malformatted articles through rnews) would not cause innd to crash.  (This
+malformatted articles through rnews) would not cause B<innd> to crash.  (This
 was not exploitable.)
 
 =item *
@@ -245,7 +238,7 @@
 
 =item *
 
-configure now looks for sendmail only in /usr/sbin and /usr/lib, not on
+C<configure> now looks for B<sendmail> only in F</usr/sbin> and F</usr/lib>, not on
 the user's path.  This should reduce the need for B<--with-sendmail> if your
 preferred sendmail is in a standard location.
 
@@ -257,14 +250,14 @@
 
 =item *
 
-innd now never decreases the high water mark of a newsgroup when
-renumbering, which should help ameliorate overview and active file
+B<innd> now never decreases the high water mark of a newsgroup when
+renumbering, which should help ameliorate overview and F<active> file
 synchronization problems.
 
 =item *
 
-Do not close and reopen the history file on ctlinnd reload when the server
-is paused or throttled.  This was breaking ctlinnd reload all during a
+Do not close and reopen the F<history> file on B<ctlinnd> reload when the server
+is paused or throttled.  This was breaking B<ctlinnd> reload all during a
 server pause.
 
 =item *
@@ -285,7 +278,7 @@
 
 =head1 Upgrading from 2.3 to 2.4
 
-The inn.conf parser has changed between S<INN 2.3> and 2.4.  Due to that
+The F<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.  S<INN 2.4> comes with a script,
@@ -305,18 +298,18 @@
 will tell INN to use the same history backend as was used in previous
 versions.  B<innupgrade> should take care of this for you.
 
-ovdb is known to have some locking and timing issues related to how nnrpd
+ovdb is known to have some locking and timing issues related to how B<nnrpd>
 shuts down (or fails to shut down) the overview databases.  If you have
-stability problems with ovdb, try setting readserver to true in
+stability problems with ovdb, try setting I<readserver> to C<true> in
 F<ovdb.conf>.  This will funnel all ovdb reads through a single process
 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
+If you use Perl authentication for B<nnrpd> (if I<nnrpdperlauth> in
+F<inn.conf> is C<true>), there have been major changes.  See "Changes to
 Perl Authentication Support for nnrpd" in F<doc/hook-perl> for details.
 
-Similarly, if you use Python authentication for nnrpd (if
-I<nnrpdpythonauth> in F<inn.conf> is true), there have been major changes.
+Similarly, if you use Python authentication for B<nnrpd> (if
+I<nnrpdpythonauth> in F<inn.conf> is C<true>), there have been major changes.
 See "Changes to Python Authentication and Access Control Support for
 nnrpd" in F<doc/hook-python> for details.
 
@@ -330,8 +323,8 @@
 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 S<INN 2.3>, see L<"Upgrading
-from 2.2 to 2.3">.
+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
 
@@ -361,7 +354,7 @@
 
 =item *
 
-nnrpd now optionally supports article injection via IHAVE, see
+B<nnrpd> now optionally supports article injection via IHAVE, see
 readers.conf(5).  Any articles injected this way must have Date, From,
 Message-ID, Newsgroups, Path, and Subject headers.  X-Trace and
 X-Complaints-To headers will be added if the appropriate options are set
@@ -371,13 +364,13 @@
 
 =item *
 
-nnrpd now handles arbitrarily long lines in POST and IHAVE; administrators
+B<nnrpd> now handles arbitrarily long lines in POST and IHAVE; administrators
 who want to limit the length of lines in locally posted articles will need
 to add this to their local filters instead.
 
 =item *
 
-nnrpd no longer handles the poorly-specified S<RFC 977> optional fourth
+B<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.
 
@@ -387,16 +380,16 @@
 
 =item *
 
-nnrpd no longer accepts UTC as a synonym for GMT for NEWGROUPS or NEWNEWS.
+B<nnrpd> no longer accepts UTC as a synonym for GMT for NEWGROUPS or NEWNEWS.
 This usage was never portable, and was rejected by the NNTP working group.
 It is being removed now in the hope that it will be caught before anyone
 starts to rely on it.
 
 =item *
 
-innfeed supports a new peer parameter, I<backlog-feed-first>, that if set
-to true feeds any backlog to a peer before new articles, see
-innfeed.conf(5).  When used in combination with I<max-connections: 1>,
+B<innfeed> supports a new peer parameter, I<backlog-feed-first>, that if set
+to C<true> feeds any backlog to a peer before new articles, see
+innfeed.conf(5).  When used in combination with I<max-connections> set to C<1>,
 this can be used to enforce in-order delivery of messages to a peer that
 is doing Xref slaving, avoiding cases where a higher-numbered message is
 received before a lower-numbered message in the same group.
@@ -404,9 +397,9 @@
 =item *
 
 Several other, more minor protocol issues have been fixed:  connections
-rejected due to the connection rate limiting in innd receive 400 replies
-instead of 504 or 505, and ARTICLE without an argument will always either
-retrieve the current article or return a 423 error, never advance the
+rejected due to the connection rate limiting in B<innd> receive C<400> replies
+instead of C<504> or C<505>, and ARTICLE without an argument will always either
+retrieve the current article or return a C<423> error, never advance the
 current article number to the next valid article.
 
 See F<doc/compliance-nntp> for all of the known issues with INN's
@@ -414,7 +407,7 @@
 
 =item *
 
-All accesses to the history file for all parts of INN now go through a
+All accesses to the F<history> file for all parts of INN now go through a
 generic API like the storage and overview subsystems do.  This will
 eventually allow new history implementations to be dropped in without
 affecting the rest of INN, and will significantly improve the
@@ -429,7 +422,7 @@
 values must be included in F<inn.conf> even if using the defaults for the
 use of shell or Perl scripts, and it will serve as the basis for
 standardizing and cleaning up the configuration file parsing in other
-parts of INN.  B<innupgrade> is run during make update and should convert
+parts of INN.  B<innupgrade> is run during C<make update> and should convert
 an existing F<inn.conf> file for you.
 
 =item *
@@ -443,9 +436,9 @@
 
 =item *
 
-Two configure options have changed names:  B<--with-tmp-path> is now
+Two C<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.
+improve consistency and better match the C<autoconf> option guidelines.
 
 =item *
 
@@ -464,8 +457,8 @@
 
 Two new options, I<nfsreader> and I<nfswriter>, have been added to
 F<inn.conf> to aid in building NFS based shared reader/writer platforms.
-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
+On the writer server configure I<nfswriter> to C<true> and on all of the readers
+configure I<nfsreader> to C<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 S<Solaris 8>,
 using CNFS as the storage mechanism and tradindexed as the overview
@@ -474,13 +467,13 @@
 =item *
 
 A new option, I<tradindexedmmap>, has been added to F<inn.conf>.  If set
-to true (the default), then the tradindexed overview method will use
+to C<true> (the default), then the tradindexed overview method will use
 mmap() to access its overview data (in 2.3 you couldn't control this; it
 always used mmap).
 
 =item *
 
-Thanks to code contributed by CMU, innfeed can now feed an IMAP server as
+Thanks to code contributed by CMU, B<innfeed> can now feed an IMAP server as
 well as other NNTP servers.  See the man page for innfeed(8) for more
 information.
 
@@ -494,12 +487,12 @@
 The wildmat functions in INN now support UTF-8, in a way that should allow
 them to still work with most simple 8-bit character sets in widespread
 use.  As part of this change, some additional wildmat interfaces are now
-available and the names have changed (to uwildmat, where u is for
+available and the names have changed (to uwildmat, where C<u> is for
 Unicode).  See uwildmat(3) for the details.
 
 =item *
 
-The interface between external authenticators and nnrpd is now properly
+The interface between external authenticators and B<nnrpd> is now properly
 documented, in F<doc/external-auth>.  A library implementing this
 interface in C is provided, which should make it easier to write
 additional authenticators resolvers.  See libauth(3) for details, and any
@@ -518,20 +511,20 @@
 
 =item *
 
-Clients using POST are no longer permitted to provide an Injector-Info
+Clients using POST are no longer permitted to provide an Injector-Info:
 header.
 
 =item *
 
-Fixed a bug causing posts with Followup-To set to a moderated group to be
+Fixed a bug causing posts with Followup-To: set to a moderated group to be
 rejected if the posting user didn't have permission to approve postings.
 
 =item *
 
-Fixed bugs in inncheck with setuid rnews or setgid inews, in innconfval
-with inn.conf parameters containing shell metacharacters but no spaces,
-and in parsedate.y with some versions of yacc.  Fixed a variety of
-size-related printf format warnings (e.g., %d vs. %ld) thanks to the work
+Fixed bugs in B<inncheck> with setuid rnews or setgid inews, in I<innconfval>
+with F<inn.conf> parameters containing shell metacharacters but no spaces,
+and in F<parsedate.y> with some versions of B<yacc>.  Fixed a variety of
+size-related printf format warnings (e.g., C<%d> vs. C<%ld>) thanks to the work
 of Winfried Szukalski.
 
 =back
@@ -558,23 +551,23 @@
 
 =item *
 
-Two bugs in pgpverify when using GnuPG were fixed: it now correctly checks
-for gpgv (rather than pgp) when told to use GnuPG and expects the keyring
-to be pubring.gpg (not pubring.pgp).
+Two bugs in B<pgpverify> when using GnuPG were fixed:  it now correctly checks
+for B<gpgv> (rather than B<pgp>) when told to use GnuPG and expects the keyring
+to be F<pubring.gpg> (not F<pubring.pgp>).
 
 =item *
 
-Substantial updates to the sample provided control.ctl file.
+Substantial updates to the sample provided F<control.ctl> file.
 
 =item *
 
 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
+Linux (including with large file support), and Tru64.  B<inndf> fixes for
 ReiserFS.
 
 =item *
 
-Various bugs in the header handling in nnrpd have been fixed, including
+Various bugs in the header handling in B<nnrpd> have been fixed, including
 hangs when using virtual domains and improper processing of folded headers
 under certain circumstances.
 
@@ -590,10 +583,10 @@
 
 =item *
 
-pgpverify now supports using GnuPG to check signatures (rather than PGP)
-without the pgpgpg wrapper.  GnuPG can check both old-style RSA signatures
-and new OpenPGP signatures and is recommended over PGP 2.6.  If you have
-GnuPG installed, pgpverify will use it rather than PGP, which means that
+B<pgpverify> now supports using GnuPG to check signatures (rather than PGP)
+without the B<pgpgpg> wrapper.  GnuPG can check both old-style RSA signatures
+and new OpenPGP signatures and is recommended over S<PGP 2.6>.  If you have
+GnuPG installed, B<pgpverify> will use it rather than PGP, which means that
 you may have to create a new key ring for GnuPG to use to verify signatures
 if you were previously using PGP.
 
@@ -601,19 +594,19 @@
 
 Users can no longer post articles containing Approved: headers to
 moderated groups by default; they must be specifically given that
-permission with the access: parameter in readers.conf.  See the man page
+permission with the I<access> parameter in F<readers.conf>.  See the man page
 for more details.
 
 =item *
 
 Two bugs in repacking overview index files and a reliability bug with
 writing overview data were all fixed in the tradindexed overview method,
-hopefully making it somewhat more reliable, particularly for makehistory.
+hopefully making it somewhat more reliable, particularly for B<makehistory>.
 
 =item *
 
-If rc.news.local exists in the INN binary directory, it will be run with
-the start or stop argument whenever rc.news is run.  This is available
+If F<rc.news.local> exists in the INN binary directory, it will be run with
+the start or stop argument whenever B<rc.news> is run.  This is available
 as a hook for local startup and shutdown code.
 
 =item *
@@ -624,17 +617,17 @@
 
 =item *
 
-The sample control.ctl file has been extensively updated.
+The sample F<control.ctl> file has been extensively updated.
 
 =item *
 
-Wildmat exclusions (@ and !) should now work properly in storage.conf
+Wildmat exclusions (C<@> and C<!>) should now work properly in F<storage.conf>
 newsgroup patterns.
 
 =item *
 
-The implementation of the -w flag for expireover was fixed; previously,
-the value given to -w to change expireover's notion of the current time
+The implementation of the B<-w> flag for B<expireover> was fixed; previously,
+the value given to B<-w> to change B<expireover>'s notion of the current time
 was scaled by too much.
 
 =item *
@@ -650,7 +643,7 @@
 
 =item *
 
-innxmit can again handle regular filenames as input as well as storage API
+B<innxmit> can again handle regular filenames as input as well as storage API
 tokens (allowing it to be used to import an old traditional spool).
 
 =item *
@@ -660,24 +653,24 @@
 
 =item *
 
-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
+A very long-standing (since S<INN 1.0>!) NNTP protocol bug in B<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 I<possibly> cause problems with some
 Netscape browsers, but other news servers correctly follow the protocol.
 
 =item *
 
 Some serious performance problems with expiration of tradspool should now
 be at least somewhat alleviated.  tradspool and timehash now know how to
-output file names for removal rather than tokens, and fastrm's ability to
+output file names for removal rather than tokens, and B<fastrm>'s ability to
 remove regular files has been restored.  This should bring expiration
 times for tradspool back to within a factor of two of pre-storage-API
 expiration times.
 
 =item *
 
-Added a sample subscriptions file and documentation for it and innmail.
+Added a sample F<subscriptions> file and documentation for it and B<innmail>.
 
 =back
 
@@ -687,15 +680,15 @@
 
 =item *
 
-inews no longer downloads the active file, no longer tries to send
+B<inews> no longer downloads the F<active> file, no longer tries to send
 postings to moderated groups to the moderator directly, and in general
-duplicates less of the functionality of nnrpd, instead letting nnrpd
-handle it.  This fixes the problem of inews not working properly for users
+duplicates less of the functionality of B<nnrpd>, instead letting B<nnrpd>
+handle it.  This fixes the problem of B<inews> not working properly for users
 other than news without being setgid.
 
 =item *
 
-Added a man page for ckpasswd.
+Added a man page for B<ckpasswd>.
 
 =item *
 
@@ -709,7 +702,7 @@
 
 =item *
 
-INN now complaints loudly at configure time if the configured path for
+INN now complains loudly at C<configure> time if the configured path for
 temporary files is world-writeable, since this configuration can be a
 security hole.
 
@@ -722,44 +715,44 @@
 =head1 Upgrading from 2.2 to 2.3
 
 There may be additional things to watch out for not listed here; if you
-run across any, please let inn-bugs at isc.org know about them.
+run across any, please let <inn-bugs at isc.org> know about them.
 
-Simply doing a make update is not sufficient to upgrade; the history and
+Simply doing a C<make update> is not sufficient to upgrade; the history and
 overview information will also have to be regenerated, since the formats
 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 S<INN 2.2>.  A
-good default storage.conf file for 2.2 users would be:
+F<storage.conf> file, if you weren't using the storage API under S<INN 2.2>.  A
+good default F<storage.conf> file for 2.2 users would be:
 
     method tradspool {
         newsgroups: *
         class: 0
     }
 
-Create this storage.conf file before rebuilding history or overview.
+Create this F<storage.conf> file before rebuilding history or overview.
 
 If you want to allow readers, or if you want to expire based on newsgroup
 name, you need to tell INN to generate overview data and pick an overview
-method by setting I<ovmethod> in F<inn.conf>.  See INSTALL and inn.conf(5)
+method by setting I<ovmethod> in F<inn.conf>.  See F<INSTALL> and inn.conf(5)
 for more details.
 
-The code that generates the dbz index files has been split into a seperate
-program, F<makedbz>.  F<makehistory> still generates the base history file
+The code that generates the dbz index files has been split into a separate
+program, B<makedbz>.  B<makehistory> still generates the base F<history> file
 and the overview information, but some of its options have been changed.
 To rebuild the history and overview files, use something like:
 
     makehistory -b -f history.n -O -T /usr/local/news/tmp -l 600000
 
 (change the F</usr/local/news/tmp> path to some directory that has plenty of
-temporary space, and leave off -O if you're running a transit-only server
+temporary space, and leave off B<-O> if you're running a transit-only server
 and don't intend to expire based on group name, and therefore don't need
 overview.)  Or if your overview is buffindexed, use:
 
     makehistory -b -f history.n -O -F
 
 Both will generate a new history file as F<history.n> and rebuild overview
-at the same time.  If you want to preseve a record of expired message IDs
+at the same time.  If you want to preseve a record of expired Message-IDs
 in the history file, run:
 
     awk 'NF==2 { print; }' < history >> history.n
@@ -768,13 +761,13 @@
 new history file and make sure it looks right, then generate the new index
 files and move them into place:
 
-    makedbz -s `wc -l <history.n` -f history.n
+    makedbz -s `wc -l < history.n` -f history.n
     mv history.n history
     mv history.n.dir history.dir
     mv history.n.hash history.hash
     mv history.n.index history.index
 
-(Rather than .hash and .index files, you may have a .pag file if you're
+(Rather than F<.hash> and F<.index> files, you may have a F<.pag> file if you're
 using tagged hash.)
 
 For reader machines, F<nnrp.access> has been replaced by F<readers.conf>.
@@ -796,16 +789,16 @@
 or making it optional, to add support for Diablo-style header feeds and
 pull-on-demand of articles from a master server.)
 
-The flags for F<overchan> have changed, plus you probably don't want to
-run overchan at all any more.  Letting innd write overview data itself
+The flags for B<overchan> have changed, plus you probably don't want to
+run B<overchan> at all any more.  Letting B<innd> write overview data itself
 results in somewhat slower performance, but is more reliable and has a
 better failure mode under high loads.  Writing overview data directly is
 the default, so in a normal upgrade from 2.2 to 2.3 you'll want to comment
-out or remove your overchan entry in F<newsfeeds> and set useoverchan to
-false in F<inn.conf>.
+out or remove your B<overchan> entry in F<newsfeeds> and set I<useoverchan> to
+C<false> in F<inn.conf>.
 
-F<crosspost> is no longer installed, and no longer works (even with
-traditional spool).  If you have an entry for crosspost in F<newsfeeds>,
+B<crosspost> is no longer installed, and no longer works (even with
+traditional spool).  If you have an entry for B<crosspost> in F<newsfeeds>,
 remove it.
 
 If you're importing a traditional spool from a pre-storage API INN server,
@@ -814,8 +807,8 @@
 the old spool.  It's more reliable and ensures that everything gets put
 into the right place.  The easiest way to do this is to generate, on your
 old server, a list of all of your existing article files and then feed
-that list to innxmit.  Further details can be found in the FAQ at
-I<http://www.eyrie.org/~eagle/faqs/inn.html>.
+that list to B<innxmit>.  Further details can be found in the FAQ at
+L<http://www.eyrie.org/~eagle/faqs/inn.html>.
 
 If you are using a version of Cleanfeed that still has a line in it like:
 
@@ -868,7 +861,7 @@
 
 =item *
 
-INN now supports embedded Python filters as well as Perl and TCL filters,
+INN now supports embedded Python filters as well as Perl and Tcl filters,
 and supports Python authentication hooks.
 
 =item *
@@ -879,9 +872,9 @@
 
 To simplify anti-abuse filtering, and to be more compliant with news
 standards and proposed standards, INN now treats as control messages only
-articles containing a Control header.  A Subject line beginning with
+articles containing a Control: header.  A Subject: line beginning with
 C<cmsg > is no longer sufficient for a message to be considered a control
-message, and the Also-Control header is no longer supported.
+message, and the Also-Control: header is no longer supported.
 
 =item *
 
@@ -894,8 +887,8 @@
 The build and installation system has been substantially overhauled.
 C<make update> now updates scripts as well as binaries and documentation,
 there is better support for parallel builds (C<make -j>), there is less
-make recursion, and far more of the system-dependent configuration is
-handled directly by autoconf.  libtool build support (including shared
+C<make> recursion, and far more of the system-dependent configuration is
+handled directly by C<autoconf>.  libtool build support (including shared
 library support) should be better than previous releases.
 
 =back
@@ -906,18 +899,18 @@
 
 =item *
 
-inews is not installed setgid news and rnews is not installed setuid root
+B<inews> is not installed setgid news and B<rnews> is not installed setuid root
 by default any more.  If you need the old permissions, you have to give a
 flag to configure.  See F<INSTALL> for more details.
 
 =item *
 
-Fixed a security hole when verifycancels was enabled in inn.conf (not the
+Fixed a security hole when I<verifycancels> was enabled in F<inn.conf> (not the
 default).
 
 =item *
 
-Message IDs are now limited to 250 octets to prevent interoperability
+Message-IDs are now limited to 250 octets to prevent interoperability
 problems with other servers.
 
 =item *
@@ -937,7 +930,7 @@
 =item *
 
 Various minor bug fixes and a Y2K bug fix.  The Y2K bug is in version
-version 2.2.1 only and will show up after Jan 1st, 2000 when a news reader
+version 2.2.1 only and will show up after S<Jan 1st>, 2000 when a news reader
 issues a NEWNEWS command for a date prior to the year 2000.
 
 =back
@@ -953,54 +946,56 @@
 
 =back
 
-=head1 Changes in 2.1
+=head1 Changes in 2.2
 
 =over 2
 
 =item *
 
-New storage.conf file (replaces storage.ctl).
+New F<storage.conf> file (replaces F<storage.ctl>).
 
 =item *
 
-New (optional) way of handling non-cancel control messages (controlchan)
+New (optional) way of handling non-cancel control messages (B<controlchan>)
 that serializes them and prevents server overload from control message
 storms.
 
 =item *
 
-Support for actsyncd to fetch active file with ftp; configured by default
-to use <ftp://ftp.isc.org/pub/usenet/CONFIG/active.Z> if you run actsyncd.
-Be sure to read the manual page for actsync to configure an actsync.ign
-file for your site, and test simpleftp if you do not configure with wget
-or ncftp.  Also see <ftp://ftp.isc.org/pub/usenet/CONFIG/README>.
+Support for B<actsyncd> to fetch F<active> file with B<ftp>; configured by default
+to use L<ftp://ftp.isc.org/pub/usenet/CONFIG/active.Z> if you run B<actsyncd>.
+Be sure to read the manual page for B<actsync> to configure an F<actsync.ign>
+file for your site, and test B<simpleftp> if you do not C<configure> with B<wget>
+or B<ncftp>.  Also see L<ftp://ftp.isc.org/pub/usenet/CONFIG/README>.
 
 =item *
 
-Some options to configure are now moved to inn.conf (merge-to-groups and
-pgp-verify).
+Some options to C<configure> are now moved to F<inn.conf> (I<merge-to-groups> and
+I<pgp-verify>, without the hyphen).
 
 =item *
 
-inndf, a portable version of df(1), is supplied.
+B<inndf>, a portable version of df(1), is supplied.
 
 =item *
 
-New cnfsstat program to show stats of cnfs buffers.
+New B<cnfsstat> program to show stats of CNFS buffers.
 
 =item *
 
-news2mail and mailpost programs for gatewaying news to mail and mail to
+B<news2mail> and B<mailpost> programs for gatewaying news to mail and mail to
 news are supplied.
 
 =item *
 
-pullnews program for doing a sucking feed is provided (not meant for large
+B<pullnews> program for doing a sucking feed is provided (not meant for large
 feeds).
 
 =item *
 
-The innshellvars.csh.in script is obsolete (and lives in the obsolete
+The B<innshellvars.csh.in> script is obsolete (and lives in the F<obsolete>
 directory, for now).
 
 =back
+
+=cut



More information about the inn-committers mailing list