INN commit: trunk/doc/pod (3 files)

[INN Commit]

    Date: Friday, August 10, 2007 @ 10:48:06
  Author: iulius
Revision: 7643

Typos.

Modified:
  trunk/doc/pod/buffchan.pod
  trunk/doc/pod/buffindexed.conf.pod
  trunk/doc/pod/storage.conf.pod

----------------------+
 buffchan.pod         |   11 ++++++-----
 buffindexed.conf.pod |    5 +++--
 storage.conf.pod     |   18 +++++++++---------
 3 files changed, 18 insertions(+), 16 deletions(-)

Modified: buffchan.pod
===================================================================
--- buffchan.pod	2007-08-10 11:25:05 UTC (rev 7642)
+++ buffchan.pod	2007-08-10 17:48:06 UTC (rev 7643)
@@ -26,8 +26,9 @@
 options.
 
 As an exploder feed (see newsfeeds(5) for an explanation), B<buffchan>
-interprets lines beginning with an exclamation point as commands.  There
-are three supported commands:
+interprets lines beginning with an exclamation point as commands.  Besides
+C<!begin> (which only marks the start of the feed), there are three
+supported commands:
 
 =over 4
 
@@ -91,7 +92,7 @@
 
 This flag may be used to specify a directory the program should change to
 before starting.  If this flag is used, the default for the B<-s> flag
-(see below) is changed to be a simple "%s" (in other words, output files
+(see below) is changed to be a simple C<%s> (in other words, output files
 are considered to be relative to I<directory>).
 
 =item B<-f> I<num-fields>
@@ -144,9 +145,9 @@
 The B<-s> flag may be used to specify a format that maps a filename from
 the filename fields at the end of each line to an actual filename.  This
 is a sprintf(3) format string that should contain a single instance of
-"%s", which will be replaced with the value of the filename field
+C<%s>, which will be replaced with the value of the filename field
 (possibly after mapping with the map file from B<-m>).  The default value
-is I<pathoutgoing>/%s.
+is I<pathoutgoing>/C<%s>.
 
 =item B<-u>
 

Modified: buffindexed.conf.pod
===================================================================
--- buffindexed.conf.pod	2007-08-10 11:25:05 UTC (rev 7642)
+++ buffindexed.conf.pod	2007-08-10 17:48:06 UTC (rev 7643)
@@ -44,7 +44,7 @@
 <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 byte).  If
+<size> is the length of the buffer in kilobytes (1KB = 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
@@ -122,7 +122,7 @@
     major=`ls -Ll "$1" | awk '{print $5}' | tr -d ,`
     minor=`ls -Ll "$1" | awk '{print $6}`
     mkdir -p /usr/local/news/spool/overview
-    mknod /usr/local/news/spool/overvew/"$base" b "$major" "$minor"
+    mknod /usr/local/news/spool/overview/"$base" b "$major" "$minor"
     chown news:news /usr/local/news/spool/overview/"$base"
     chmod 644 /usr/local/news/spool/overview/"$base"
 
@@ -144,6 +144,7 @@
 
 expireover(8),
 inn.conf(5),
+inndf(8),
 makehistory(8).
 
 =cut

Modified: storage.conf.pod
===================================================================
--- storage.conf.pod	2007-08-10 11:25:05 UTC (rev 7642)
+++ storage.conf.pod	2007-08-10 17:48:06 UTC (rev 7643)
@@ -78,7 +78,7 @@
 the newsgroup names in the Newsgroups: header (see inn.conf(5) for discussion
 of the differences between these possibilities).  Poison wildmat expressions
 (expressions starting with C<@>) are allowed and can be used to exclude certain
-group patterns: articles crossposted to poisoned newsgroups will not be stored
+group patterns:  articles crossposted to poisoned newsgroups will not be stored
 using this storage method.  The <wildmat> pattern is matched in order.
 
 There is no default newsgroups pattern; if an entry should match all
@@ -179,7 +179,7 @@
 the metacycbuff into which articles matching that entry should be stored;
 see cycbuff.conf(5) for details on metacycbuffs.
 
-Advantages: By far the fastest of all storage methods (except for C<trash>),
+Advantages:  By far the fastest of all storage methods (except for C<trash>),
 since it eliminates the overhead of dealing with a file system and creating
 new files.  Unlike all other storage methods, it does not require manual
 article expiration.  With CNFS, the server will never throttle itself
@@ -187,7 +187,7 @@
 files given so that they can never use more than the amount of disk space
 allocated to them.
 
-Disadvantages: Article retention times are more difficult to control
+Disadvantages:  Article retention times are more difficult to control
 because old articles are overwritten automatically.  Attacks on Usenet,
 such as flooding or massive amounts of spam, can result in wanted articles
 expiring much faster than intended (with no warning).
@@ -207,11 +207,11 @@
 have self-expire functionality (meaning B<expire> has to run periodically
 to delete old articles).  EXPENSIVESTAT is false for this method.
 
-Advantages: It is roughly four times faster than C<timehash> for article
+Advantages:  It is roughly four times faster than C<timehash> for article
 writes, since much of the file system overhead is bypassed, while still
 retaining the same fine control over article retention time.
 
-Disadvantages: Using this method means giving up all but the most careful
+Disadvantages:  Using this method means giving up all but the most careful
 manually fiddling with the article spool; in this aspect, it looks like
 C<cnfs>.  As one of the newer and least widely used storage types,
 C<timecaf> has not been as thoroughly tested as the other methods.
@@ -230,10 +230,10 @@
 documented above under C<timecaf>).  This method does not have self-expire
 functionality.  EXPENSIVESTAT is true for this method.
 
-Advantages: Heavy traffic groups do not cause bottlenecks, and a fine control
+Advantages:  Heavy traffic groups do not cause bottlenecks, and a fine control
 of article retention time is still possible.
 
-Disadvantages: The ability to easily find all articles in a given newsgroup
+Disadvantages:  The ability to easily find all articles in a given newsgroup
 and manually fiddle with the article spool is lost, and INN still suffers
 from speed degradation due to file system overhead (creating and deleting
 individual files is a slow operation).
@@ -254,14 +254,14 @@
 used by C News and earlier news systems.  This method does not have
 self-expire functionality.  EXPENSIVESTAT is true for this method.
 
-Advantages: It is widely used and well-understood; it can read article
+Advantages:  It is widely used and well-understood; it can read article
 spools written by older versions of INN and it is compatible with all
 third-party INN add-ons.  This storage mechanism provides easy and direct
 access to the articles stored on the server and makes writing programs
 that fiddle with the news spool very easy, and gives fine control over
 article retention times.
 
-Disadvantages: It takes a very fast file system and I/O system to keep up with
+Disadvantages:  It takes a very fast file system and I/O system to keep up with
 current Usenet traffic volumes due to file system overhead.  Groups with heavy
 traffic tend to create a bottleneck because of inefficiencies in storing large
 numbers of article files in a single directory.  It requires a nightly expire