INN commit: branches/2.5 (backends/nntpsend.in doc/pod/nntpsend.pod)

INN Commit rra at isc.org
Thu May 20 19:25:13 UTC 2010


    Date: Thursday, May 20, 2010 @ 12:25:13
  Author: iulius
Revision: 9064

Fix the documentation of the -n flag for nntpsend.

Modified:
  branches/2.5/backends/nntpsend.in
  branches/2.5/doc/pod/nntpsend.pod

----------------------+
 backends/nntpsend.in |    2 +-
 doc/pod/nntpsend.pod |    5 ++---
 2 files changed, 3 insertions(+), 4 deletions(-)

Modified: backends/nntpsend.in
===================================================================
--- backends/nntpsend.in	2010-05-20 19:24:45 UTC (rev 9063)
+++ backends/nntpsend.in	2010-05-20 19:25:13 UTC (rev 9064)
@@ -12,7 +12,7 @@
 ##	-d		same as -d, and run innxmit with debug as well
 ##	-l		innxmit, log rejected articles
 ##	-N		innxmit, disable streaming mode
-##	-n		do not lock for nntpsend, do not sleep between sets
+##	-n		do not lock for nntpsend
 ##	-P portnum	port number to use
 ##	-p		run innxmit with -p to prune batch files
 ##	-r		innxmit, don't requeue on unexpected error code

Modified: doc/pod/nntpsend.pod
===================================================================
--- doc/pod/nntpsend.pod	2010-05-20 19:24:45 UTC (rev 9063)
+++ doc/pod/nntpsend.pod	2010-05-20 19:25:13 UTC (rev 9064)
@@ -44,9 +44,8 @@
 
 =item B<-n>
 
-If the B<-n> flag is used, then B<nntpsend> does not use B<shlock> and
-does not lock batch files.  It also does not sleep before spawning each
-B<innxmit> child.
+If the B<-n> flag is used, then B<nntpsend> does not use B<shlock> to lock
+the use of B<nntpsend>.  Batch files will still be locked.
 
 =item B<-s> I<size>
 




More information about the inn-committers mailing list