From 4f0663ae13490d7c8c987afae579cd414fa88ada Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Mon, 3 May 2010 17:10:49 +0100 Subject: [PATCH 1/1] manpage fixes --- doc/man/innduct.8 | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/doc/man/innduct.8 b/doc/man/innduct.8 index a4c028f..2842050 100644 --- a/doc/man/innduct.8 +++ b/doc/man/innduct.8 @@ -9,7 +9,13 @@ innduct \- quickly and reliably stream Usenet articles to remote site .SH DESCRIPTION .B innduct implements NNTP peer-to-peer news transmission including the streaming -extensions, for sending news articles to a remote site. +extensions, for sending news articles to a remote site. It is +intended as a replacement for +.I innfeed +or +.IR nntpsend +and +.IR innxmit . You need to run one instance of innduct for each peer site. innduct manages its interaction with innd, including flushing the feed as @@ -20,11 +26,10 @@ locking necessary to avoid multiple simutaneous invocations. By default, innduct reads the default feedfile corresponding to the site .I site -(is +(ie .IR pathoutgoing / site ) and feeds it via NNTP, streaming if possible, to the host .IR fqdn . - If .I fqdn is not specified, it defaults to @@ -35,10 +40,10 @@ error messages) are sent to syslog (facility .BR news ). The best way to run innduct is probably to periodically invoke innduct -for each feed (e.g. from cron), passing innduct it the +for each feed (e.g. from cron), passing the .B \-q -option to arrange that it silently exits if an innduct is already -running for that site. +option to arrange that innduct silently exits if an instance is +already running for that site. .SH INNDUCT VS INNFEED/NNTPSEND/INNXMIT .TP .B innfeed -- 2.30.2