Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

INN FAQ Part 7/9: Problems with INN already running
Section - (7.57) I upgraded to INN 1.5.1, and it takes clients a long

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Neighborhoods ]


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
See reader questions & answers on this topic! - Help others by sharing your knowledge

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.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




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 November 21 2011 @ 01:00 PM