🚀 go-pugleaf

>INN is designed for hosts on the Internet with a fair amount of memory and
>multiple fast incoming NNTP feeds.  It's a full Usenet system, but most
>traffic is NNTP.  (E.g., rnews unpacks a batch and sends it to the server
>via NNTP.)  If you do NNTP, you'll find it easier to maintain the one
>single system, rather than two.  INN is also fast, if you care about
>that.  Posting is synchronous -- when inews returns, the article has been
>written to disk and queued for forwarding.  INN puts a low, constant, load
>on your machine.

So, if we get our news via a single 56K baud line, we shouldn't
consider INN? Does our feader site also need INN running, or is
it independent of what the feeder site uses. Right now we're running
cnews and get our news in batches via nntpsend every 20 minutes.

On another note, INN *must* have more going for it than just what
is described above. What other reasons might make it worthwhile to
switch to INN. I've got it planned as a summer project but it
never hurts to plan ahead....
-- 
Peter Steele        Unix Services Manager            peter.steele@acadiau.ca 
Acadia Univ., Wolfville, NS, Canada B0P 1X0  902-542-2201  Fax: 902-542-4364