INN commit: trunk/doc/pod (cycbuff.conf.pod install.pod)

[INN Commit]

    Date: Sunday, June 14, 2015 @ 05:23:50
  Author: iulius
Revision: 9900

Improve documentation for CNFS buffers larger than 2 GB

Large-file support is useful only for 32-bit platforms (and some very
rare 64-bit platforms that aren't Linux).

Modified:
  trunk/doc/pod/cycbuff.conf.pod
  trunk/doc/pod/install.pod

------------------+
 cycbuff.conf.pod |   20 +++++++++++---------
 install.pod      |   18 ++++++++++--------
 2 files changed, 21 insertions(+), 17 deletions(-)

Modified: cycbuff.conf.pod
===================================================================
--- cycbuff.conf.pod	2015-06-14 11:44:57 UTC (rev 9899)
+++ cycbuff.conf.pod	2015-06-14 12:23:50 UTC (rev 9900)
@@ -10,15 +10,17 @@
 if the CNFS (Cyclic News File System) storage method is used.  INN will
 look for it in I<pathetc> (as set in F<inn.conf>).
 
-CNFS stores articles in logical objects called I<metacycbuffs>.  Each
-metacycbuff is in turn composed of one or more physical buffers called
-I<cycbuffs>.  As articles are written to the metacycbuff, each article is
-written to the next cycbuff in the list in a round-robin fashion (unless
-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 S<2 GB>,
-you need to build INN with the B<--enable-largefiles> option.
+CNFS stores articles in logical objects called I<metacycbuffs>.
+Each metacycbuff is in turn composed of one or more physical buffers
+called I<cycbuffs>.  As articles are written to the metacycbuff, each
+article is written to the next cycbuff in the list in a round-robin
+fashion (unless 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 S<2 GB> on 32-bit platforms (and some very rare
+64-bit platforms that aren't Linux), you need to build INN with the
+B<--enable-largefiles> option.
 
 For information about how to configure INN to use CNFS, see
 storage.conf(5).

Modified: install.pod
===================================================================
--- install.pod	2015-06-14 11:44:57 UTC (rev 9899)
+++ install.pod	2015-06-14 12:23:50 UTC (rev 9900)
@@ -304,11 +304,12 @@
 
 Enables large file support.  This is not enabled by default, even on
 platforms that support it, because it changes the format of INN's on-disk
-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 S<2 GB> or you want to use CNFS buffers larger than
-S<2 GB>.
+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 S<2 GB> or you want to use CNFS
+buffers larger than S<2 GB> on 32-bit platforms (and some very rare
+64-bit platforms that aren't Linux).
 
 The history, tradindexed and buffindexed overview, and timecaf databases
 written by an INN built with this option are incompatible with those
@@ -1116,9 +1117,10 @@
 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 S<2 GB>, you need to build INN with
-the B<--enable-largefiles> option.  See L<Installing INN> for more
-information and some caveats.
+In order to use any cycbuff larger than S<2 GB> on 32-bit platforms
+(and some very rare 64-bit platforms that aren't Linux), you need to
+build INN with the B<--enable-largefiles> option.  See L<Installing INN>
+for more information and some caveats.
 
 For each cycbuff you will be creating, add a line to F<cycbuff.conf> like
 the following: