rkt logo

INN FAQ Part 7

Be sure to read the "RKT couplings" below for additional information and updates to this entry.

Subject: (7.57) I upgraded to INN 1.5.1, and it takes clients a long
time to connect.

This may be caused by streaming NNTP (see INN FAQ #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.


[Source: INN FAQ Part 7 Archive-name: usenet/software/inn-faq/part7]
[Last Changed: $Date: 1997/09/16 01:25:57 $ $Revision: 2.25 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]

(Corrections, notes, and links by Mib Software)
More Detailed Topics
7.56 INN FAQ I upgraded to INN 1.5.1, and peers have trouble feeding me.
alternatives to how nnrpd starts

Overview and Related Topics
Up to: INN FAQ Table Of Contents for Part 7/9
Up to: Usenet RKT For Providers...Troubleshooting INN
Up to: INN Troubleshooting by Topic: Performance

RKT Rapid-Links:[ Search ] [ RKT Tips ] Path: Usenet RKT / For / INN FAQ / Part 7 / 0065.htm

You are reading from the Usenet RKT
Copyright 1997-1999, Forrest J. Cavalier III, Mib Software
INN customization and consulting
E-mail comments