Xref: utzoo gnu.emacs.gnus:1035 news.software.nntp:1005 Path: utzoo!utgpu!watserv1!watmath!uunet!samsung!zaphod.mps.ohio-state.edu!wuarchive!bcm!tmc.edu!sob From: nntp@tmc.edu Newsgroups: gnu.emacs.gnus,news.software.nntp Subject: Re: gnus broken!? Message-ID: <3336@gazette.bcm.tmc.edu> Date: 21 Dec 90 22:38:08 GMT References: <1990Dec5.181808.10759@mprgate.mpr.ca> Sender: usenet@bcm.tmc.edu Followup-To: gnu.emacs.gnus Organization: Baylor College of Medicine, Houston, Tx Lines: 30 Nntp-Posting-Host: tmc.edu Originator: sob@tmc.edu In article cedman@golem.ps.uci.edu (Carl Edman) writes: >The problem is a bug in the NNTP software revision 1.5.10. It didn't >exist in 1.5.9 and has been promised to be fixed in 1.5.11. Basically >the problem is that NNTP mixes 2 levels of file access. It uses >buffered IO, and at the same time uses select(). Usually this doesn't >cause any trouble as long as the sender of commands doesn't send them >faster than they can be processed, so that the buffer is always empty >when NNTP looks for the next command. But GNUS requires a large number >of commands at a decent speed, so it sends up to 400 commands ahead >before waiting for a reply. We are in alpha testing of nntp 1.5.11 now and early results are that the "gnus" problem is fixed. Expect to see 1.5.11 hit the streets around February 1, 1991. It will also fix the "pipe" problem reported by some. We are also looking into fixing the 4096 articles/group problem that some people are afraid of happening. We hope to release a new version of clientlib that will work with TLI as well. Please send any questions to "nntp@tmc.edu" -- Stan internet: sob@bcm.tmc.edu Director, Networking Olan uucp: {rutgers,mailrus}!bcm!sob and Systems Support Barber Opinions expressed are only mine. Baylor College of Medicine