[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 1/9: General Information
Previous Document: Table Of Contents for Part 1/9
Next Document: (1.2) I thought Rich Salz maintains INN ...
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 1/9: General Information
Previous Document: Table Of Contents for Part 1/9
Next Document: (1.2) I thought Rich Salz maintains INN ...
(1.1) What is INN?
For a complete answer, why not read the Usenix paper that introduced INN to the world? It's available as ftp://ftp.uu.net/networking/news/nntp/inn/inn.usenix.ps.Z InterNetNews is a complete Usenet system. The cornerstone of the package is innd, an NNTP server that multiplexes all I/O. Think of it as an nntpd merged with the B News inews, or as a C News relaynews that reads multiple NNTP streams. Newsreading is handled by a separate server, nnrpd, that is spawned for each client. Both innd and nnrpd have some slight variances from the NNTP protocol (although in normal use you will never notice); see the manpages. INN separates hosts that feed you news from those that have users reading news. If you need to support a mixed environment you will have to do some extra work; the installation manual gives some hints.
Top Document: INN FAQ Part 1/9: General Information
Previous Document: Table Of Contents for Part 1/9
Next Document: (1.2) I thought Rich Salz maintains INN ...
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)
Last Update September 07 2008 @ 00:13 AM