INN commit: trunk/doc/pod (6 files)
INN Commit
rra at isc.org
Sat Feb 12 10:09:24 UTC 2011
Date: Saturday, February 12, 2011 @ 02:09:24
Author: iulius
Revision: 9186
Fix spaces.
Modified:
trunk/doc/pod/actsync.pod
trunk/doc/pod/innupgrade.pod
trunk/doc/pod/innxmit.pod
trunk/doc/pod/news.pod
trunk/doc/pod/newsfeeds.pod
trunk/doc/pod/scanlogs.pod
----------------+
actsync.pod | 9 ++++-----
innupgrade.pod | 7 +++----
innxmit.pod | 2 +-
news.pod | 2 +-
newsfeeds.pod | 2 +-
scanlogs.pod | 2 +-
6 files changed, 11 insertions(+), 13 deletions(-)
Modified: actsync.pod
===================================================================
--- actsync.pod 2011-02-12 09:50:55 UTC (rev 9185)
+++ actsync.pod 2011-02-12 10:09:24 UTC (rev 9186)
@@ -449,11 +449,10 @@
=item B<-p> I<min-unchanged>
By default, the B<actsync> utility has safeguards against performing
-massive changes. If fewer than I<min-unchanged> percent of the
-non-ignored lines from the local host remain unchanged, no actions
-(output, execution, etc.) are performed and B<actsync> exits with a
-non-zero exit status. The I<min-unchanged> value may be a floating point
-value such as C<66.667>.
+massive changes. If fewer than I<min-unchanged> percent of the non-ignored
+lines from the local host remain unchanged, no actions (output, execution,
+etc.) are performed and B<actsync> exits with a non-zero exit status.
+The I<min-unchanged> value may be a floating point value such as C<66.667>.
A change is a local newsgroup line that was removed, added, changed,
or found to be in error. Changing the 2nd or 3rd F<active> fields via
Modified: innupgrade.pod
===================================================================
--- innupgrade.pod 2011-02-12 09:50:55 UTC (rev 9185)
+++ innupgrade.pod 2011-02-12 10:09:24 UTC (rev 9186)
@@ -53,10 +53,9 @@
=item *
-If the F<sasl.conf> file exists, its content is merged in
-the I<tlscapath>, I<tlscafile>, I<tlscertfile> and I<tlskeyfile>
-parameters introduced in S<INN 2.5>. The file is then renamed to
-F<sasl.conf.OLD>.
+If the F<sasl.conf> file exists, its content is merged in the I<tlscapath>,
+I<tlscafile>, I<tlscertfile> and I<tlskeyfile> parameters introduced in
+S<INN 2.5>. The file is then renamed to F<sasl.conf.OLD>.
=back
Modified: innxmit.pod
===================================================================
--- innxmit.pod 2011-02-12 09:50:55 UTC (rev 9185)
+++ innxmit.pod 2011-02-12 10:09:24 UTC (rev 9186)
@@ -109,7 +109,7 @@
=item B<-t> I<seconds>
B<innxmit> normally blocks until the connection is made. To specify a timeout
-on how long to try to make the connection, use the B<-t> flag.
+on how long to try to make the connection, use the B<-t> flag.
=item B<-v>
Modified: news.pod
===================================================================
--- news.pod 2011-02-12 09:50:55 UTC (rev 9185)
+++ news.pod 2011-02-12 10:09:24 UTC (rev 9186)
@@ -823,7 +823,7 @@
=item *
-B<gpgverify> is no longer included in INN, B<pgpverify> now has better
+B<gpgverify> is no longer included in INN, B<pgpverify> now has better
support for GnuPG and should be used instead.
=item *
Modified: newsfeeds.pod
===================================================================
--- newsfeeds.pod 2011-02-12 09:50:55 UTC (rev 9185)
+++ newsfeeds.pod 2011-02-12 10:09:24 UTC (rev 9186)
@@ -45,7 +45,7 @@
article should be forwarded to a site. (A "site" is the generic term for
some destination of newsfeed data; it often corresponds to a remote news
peer, but doesn't have to. For example, a local archiving program run
-from F<newsfeeds> is also a "site.") If I<sitename> already appears in
+from F<newsfeeds> is also a "site".) If I<sitename> already appears in
the article's Path: header, then the article will not be sent to the site.
The name is usually whatever the remote site uses to identify itself in
the Path: header, but can be almost any word.
Modified: scanlogs.pod
===================================================================
--- scanlogs.pod 2011-02-12 09:50:55 UTC (rev 9185)
+++ scanlogs.pod 2011-02-12 10:09:24 UTC (rev 9186)
@@ -20,7 +20,7 @@
By default, B<scanlogs> rotates and cleans out the logs. It keeps up to
I<logcycles> old compressed log files in I<pathlog>/OLD (the I<logcycles>
-parameter can be set in F<inn.conf>). B<scanlogs> also keeps archives
+parameter can be set in F<inn.conf>). B<scanlogs> also keeps archives
of the F<active> file in this directory.
It invokes B<tally.control> if F<newgroup.log> or F<rmgroup.log> exists
More information about the inn-committers
mailing list