It has grown a bit

diff --git a/doc/man/innduct.8 b/doc/man/innduct.8
index b6c314507caa4d199ce948050c5e02a73b2763b4..580f317ed853af04e96c463253e3b87fb1c4913a 100644 (file)
--- a/doc/man/innduct.8
+++ b/doc/man/innduct.8
@@ -51,7 +51,7 @@ constantly "tailing" the feed file, and where implemented uses
 to reduce the latency which would come from having to constantly poll
 the feed file.  innfeed is capable of feeding multiple peers from a
 single innfeed instance, whereas each innduct process handles exactly
-one peer.  innduct is much smaller and simpler, at 3kloc to innfeed's
+one peer.  innduct is much smaller and simpler, at <4kloc to innfeed's
 25kloc.  innfeed needs a separate wrapper 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.