dump control command

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

diff --git a/doc/man/innduct.8 b/doc/man/innduct.8
index 83aeade401744181d29a9495eeb86a6130e5d224..50e4a41affa18447af26b704da4165cbeafc4d2b 100644 (file)
--- a/doc/man/innduct.8
+++ b/doc/man/innduct.8
@@ -307,13 +307,10 @@ articles it has in hand now, and then exit.  It is harmless to cause
 innd to flush the feed (but innduct won't notice and flushing won't
 start a new feedfile; you have to leave that to innduct).
 .LP
-There are no signals that can usefully be sent to innduct to give it
-complicated instructions.  If you need to kill innduct, feel free to
-send it a
-.B SIGTERM
-or
-.B SIGKILL
-and nothing will be broken or corrupted.
+If you want to stop innduct you can send it SIGTERM or SIGINT, in
+which case it will report statistics so far and quickly exit.
+If innduct receives SIGKILL nothing will be broken or corrupted; you
+just won't see some of the article stats.
 .SH EXIT STATUS
 .TP
 .B 0
@@ -416,6 +413,10 @@ safely remove backlog files.  \fIsomething\fR may not contain \fB#\fR
 you rename it to match the pattern \fIfeedfile\fR\fB_backlog\fR*, as
 otherwise innduct may find and process the file and read it to EOF
 before you have finished creating it.
+.IP \fIfeedfile\fR_dump
+.IX Item "debug dump file"
+On request via a control connection innduct dumps a summary of its
+state to this text file.  This is mostly useful for debugging.
 .IP /etc/news/inn.conf
 .IX Item inn.conf
 Used to find