Xref: utzoo news.software.nntp:1169 news.software.nn:1695 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!samsung!caen!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!dave From: dave@boingo.med.jhu.edu (David Heath) Newsgroups: news.software.nntp,news.software.nn Subject: Re: Having nntp 1.5.11 troubles... Message-ID: <1991Mar6.195636.2408@boingo.med.jhu.edu> Date: 6 Mar 91 19:56:36 GMT References: <1991Mar4.212651.12120@cica.indiana.edu> <1991Mar6.023712.26709@cica.indiana.edu> Organization: The Johns Hopkins Hospital-Body CT Imaging Lab Lines: 39 mr@ogre.cica.indiana.edu (Michael Regoli) writes: >In jwright@cfht.hawaii.edu (Jim >Wright) writes: >>mr@ogre.cica.indiana.edu (Michael Regoli) writes: >>>... >>>N: Mar 4 15:06 (M): Lost connection to server cica.cica.indiana.edu: >>> No such file or directory >>I was having the same trouble after changing from 6.4.11 to 6.4.12. >>Not only did it generate these messages, it failed to collect many >>groups at all. And many other groups it would only collect about 5% >>of the posted articles. I was on the verge of junking nn! >All is well now that I've recompiled nn to grab articles directly >from the spool rather than from nntp itself. (Now looking back, I'm >not certain why I enabled nntp support on the server machine to begin >with. It must have been one of those days.) >>I just changed from 6.4.12 to 6.4.13. >Now I just realized I missed patch 13! Thanks, Jim-bo! ;) >>It seems to me that nn is not reacting correctly to some sort of error >>message or bogus nntp message. Actually, this sounds like a problem with nntp. It has a hard-coded limit of 4096 articles/group. When nnmaster tries to enter a group with more than 4096 articles (like junk on some systems), the remote nntpserver dies and breaks the connection. You can tell nnmaster not to collect the junk group by starting the daemon as: nnmaster -l -r C !junk "" -dave heath dave@boingo.med.jhu.edu