X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ian/git?a=blobdiff_plain;f=innduct.8;h=f4a253d4ec9d66b60a576cc4e5c1d000de24b489;hb=f4efa8223b54eadc7938f4e67a270cfe2d0fa820;hp=a51325296ad48884e1352d800f297410121d8f8b;hpb=8cf2e7d53f5d2178c6949b478c3ac7c45a84b438;p=innduct.git

diff --git a/innduct.8 b/innduct.8
index a513252..f4a253d 100644
--- 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,17 @@ separately for each peer.
 .TP
 .B innxmit
 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
+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