[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
    Search the FAQ Archives

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.56) I upgraded to INN 1.5.1, and peers have trouble feeding me.
Next Document: (7.58) My server gets slower and is busy doing io


(7.57) I upgraded to INN 1.5.1, and it takes clients a long



This may be caused by streaming NNTP (see #7.56).  Since INN
handles all incoming NNTP connections (even the ones which are passed
off to nnrpd), incoming streaming NNTP feeds may cause INN to take a
long time to respond to a newsreader client's initial connection.  The
solutions in Subject #7.56 should be equally effective in reducing
initial connection latency for newsreaders.

Or as another alternative move innd away from port 119 and accept
nnrpd connects port 119 using inetd.



Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.56) I upgraded to INN 1.5.1, and peers have trouble feeding me.
Next Document: (7.58) My server gets slower and is busy doing io

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page


[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)

Last Update October 22 2009 @ 05:35 AM

Some parts © 2009 Advameg, Inc.