INN commit: branches/2.5/doc/pod (tdx-util.pod)

[INN Commit]

    Date: Monday, February 8, 2010 @ 14:01:33
  Author: iulius
Revision: 8975

tdx-util manpage does not know of -F option for correcting errors.

Patch from Heiko Schlichting.


Also fix a few typos.

Modified:
  branches/2.5/doc/pod/tdx-util.pod

--------------+
 tdx-util.pod |   20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

Modified: tdx-util.pod
===================================================================
--- tdx-util.pod	2010-02-08 22:00:47 UTC (rev 8974)
+++ tdx-util.pod	2010-02-08 22:01:33 UTC (rev 8975)
@@ -39,8 +39,8 @@
 set to 1.
 
 To audit the entire overview database for problems, use B<-A>.  Any
-problems found will be reported to standard error.  There is not (yet) a
-corresponding option to correct the errors found.
+problems found will be reported to standard error.  Use B<-F> to correct
+the errors found.
 
 To rebuild the database for a particular newsgroup, use B<-R>.  The B<-R>
 option takes a path to a directory which contains all of the articles for
@@ -91,7 +91,7 @@
 =item B<-F>
 
 Audit the entire overview database for problems, fixing them as they're
-detected where possible. This runs the internal consistency checks built
+detected where possible.  This runs the internal consistency checks built
 into the tradindexed overview implementation, checking such things as the
 validity and reachability of all group index entries, the format of the
 individual overview entries, the correspondence of index entries to
@@ -113,8 +113,8 @@
 article number, the offset of the data for that article in the overview
 data file for that group, the length of the overview data, the time (in
 seconds since epoch) when the article arrived on the server, the time (in
-seconds since epoch) when the article should expire based on its Expires
-header (or 0 if there is no Expires header), and the storage API token of
+seconds since epoch) when the article should expire based on its Expires:
+header (or 0 if there is no Expires: header), and the storage API token of
 the article.
 
 If this option is given, the B<-n> option must also be given to specify
@@ -123,8 +123,8 @@
 =item B<-i>
 
 Dump the master index of the overview database.  This contains similar
-information to the server active file, such as high and low water marks
-and moderation status, and is the information that nnrpd hands out to
+information to the server F<active> file, such as high and low water marks
+and moderation status, and is the information that B<nnrpd> hands out to
 clients.
 
 The fields are, in order, the newsgroup name, the high water mark, the low
@@ -146,7 +146,7 @@
 Dump the overview information for a newsgroup in the format used by
 B<overchan> as input.  Each line will start with the storage API token,
 the arrival timestamp in seconds since epoch, the expires timestamp in the
-same format (or 0 if there is no Expires header), and then the overview
+same format (or 0 if there is no Expires: header), and then the overview
 data.
 
 If this option is given, the B<-n> option must also be given to specify
@@ -163,7 +163,7 @@
 C<Article:>, the storage API token for that article labelled with
 C<Token:>, the arrival date for that article on the server in S<RFC 5322> date
 format labelled with C<Arrived:>, and the expiration date for that article
-(from the Expires header) in S<RFC 5322> date format if there is any, labelled
+(from the Expires: header) in S<RFC 5322> 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
@@ -233,6 +233,6 @@
 
 =head1 SEE ALSO
 
-makehistory(8)
+makehistory(8), nnrpd(8).
 
 =cut