notice_processed zeroes the counts

[innduct.git] / innduct.8

diff --git a/innduct.8 b/innduct.8
index a51325296ad48884e1352d800f297410121d8f8b..23f93c90f34db5717202ea994f30722c6e91a0b9 100644 (file)
--- a/innduct.8
+++ b/innduct.8
@@ -1,3 +1,4 @@
+'\" t
 .TH INNDUCT 8
 .SH NAME
 innduct \- quickly and reliably stream Usenet articles to remote site
@@ -409,8 +410,8 @@ defect in the innd channel feed protocol.  innduct uses a file feed,
 constantly "tailing" the feed file, and where implemented uses
 .BR inotify (2)
 to reduce the latency which would come from having to constantly poll
-the feed file.  innduct is much smaller and simpler, at <4kloc to
-innfeed's 25kloc.  innfeed needs a separate helper script or similar
+the feed file.  innduct is much smaller and simpler, at <5kloc to
+innfeed's ~25kloc.  innfeed needs a separate helper script or similar
 infrastructure (of which there is an example in its manpage), whereas
 innduct can be run directly and doesn't need help from shell scripts.
 However, innfeed is capable of feeding multiple peers from a single
@@ -432,6 +433,16 @@ separately for each peer.
 .TP
 .B innxmit
 is the actual NNTP feeder program used by nntpsend.
+.LP
+.TS
+l l l l.
+       \fBinnfeed\fR   \fBinnduct\fR   \fBnntpsend/innxmit\fR
+realtime feed  Yes     Yes     No
+reliable       No      Yes     Yes
+source code size       24kloc  4.6kloc 1.9kloc
+invoke once for all sites      Yes     No      Yes
+number of processes    one     1/site  2/site, intermittently
+.TE
 .SH EXIT STATUS
 .TP
 .B 0
@@ -474,7 +485,7 @@ a bug.
 .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"