.B stop
Log statistics and exit. (Same effect as SIGTERM or SIGINT.)
.TP
+.B logstats
+Log statistics so far and zero the stats counters. Stats are also
+logged periodically, when an input file is completed and just before
+tidy termination.
+.TP
+.BR show
+Writes summary information about innduct's state to the current CLI
+connection.
+.TP
.BR "dump q" | a
-Writes information about innduct's state to a plain text file
+Writes the same information about innduct's state to a plain text file
.IR feedfile \fB_dump\fR.
This overwrites any previous dump. innduct does not ever delete these
dump files.
The default is
.BR 1000s .
.TP
+.BI \-\-stats-log-interval= PERIOD
+Log statistics at least every
+.IR PERIOD
+The default is
+.BR 2500s .
+.TP
.BI \-\-low-volume-thresh= "WIN-THRESH " \-\-low-volume-window= "PERIOD "
If innduct has only one connection to the peer, and has processed
fewer than
is the actual NNTP feeder program used by nntpsend.
.LP
.TS
-left;
l l l l.
\fBinnfeed\fR \fBinnduct\fR \fBnntpsend/innxmit\fR
realtime feed Yes Yes No
.SH FILES
innduct dances a somewhat complicated dance with innd to make sure
that everything goes smoothly and that there are no races. (See the
-two ascii-art diagrams in innduct.c for details of the protocol.) Do
+two ascii-art diagrams in README.states for details of the protocol.) Do
not mess with the feedfile and other associated files, other than as
explained here:
.IX Header "FILES"