Forcibly deal with stuck articles from flushing_file after flush

[innduct.git] / doc / man / innduct.8

diff --git a/doc/man/innduct.8 b/doc/man/innduct.8
index c6f8b701974f8bb7208a14e150d1a39059a2b3d2..21705a870f543ab6155731627e3eb2f998704db8 100644 (file)
--- a/doc/man/innduct.8
+++ b/doc/man/innduct.8
@@ -255,6 +255,18 @@ threshold.
 The default is
 .BR 100000s .
 .TP
+.BI \-\-flush-finish-timeout= FLUSH-FINISH-PERIOD
+If we flushed
+.IR FLUSH-FINISH-PERIOD
+ago, and are still trying to finish processing articles that were
+written to the old feed file, we forcibly and violently make sure that
+we do by abandoning and deferring all the work (which includes
+unceremoniously dropping any connections on which we've sent some of
+those articles but not yet had replies, as they're probably stuck
+somehow).
+The default is
+.BR 2000s .
+.TP
 .BI \-\-idle-timeout= PERIOD
 Connections which have had no activity for
 .IR PERIOD
@@ -331,7 +343,10 @@ should only be used by a developer in conjuction with the innduct
 source code.
 .TP
 .B flush
-Start a new feed file and trigger a flush of the feed.
+Start a new feed file and trigger a flush of the feed.  (Or, cause
+the
+.I FLUSH-FINISH-PERIOD
+to expire early, forcibly completing a previously started flush.)
 .TP
 .B stop
 Log statistics and exit.  (Same effect as SIGTERM or SIGINT.)