From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/18990 Path: main.gmane.org!not-for-mail From: Felix Lee Newsgroups: gmane.emacs.gnus.general Subject: Re: Pterodactyl Gnus v0.52 is released Date: Fri, 20 Nov 1998 06:59:14 -0800 Sender: owner-ding@hpc.uh.edu Message-ID: <199811201459.JAA10484@sclp3.sclp.com> References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035157421 9205 80.91.224.250 (20 Oct 2002 23:43:41 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:43:41 +0000 (UTC) Cc: ding@gnus.org Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id JAA10497 for ; Fri, 20 Nov 1998 09:59:54 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.1/8.9.1) with ESMTP id IAB20552; Fri, 20 Nov 1998 08:59:42 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 20 Nov 1998 08:59:34 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id IAA23893 for ; Fri, 20 Nov 1998 08:59:27 -0600 (CST) Original-Received: from mail1.teleport.com (mail1.teleport.com [192.108.254.26]) by sclp3.sclp.com (8.8.5/8.8.5) with SMTP id JAA10484 for ; Fri, 20 Nov 1998 09:59:18 -0500 (EST) Original-Received: (qmail 3544 invoked from network); 20 Nov 1998 14:59:16 -0000 Original-Received: from pdx57-i48-14.teleport.com (HELO teleport.com) (204.202.167.92) by mail1.teleport.com with SMTP; 20 Nov 1998 14:59:16 -0000 Original-To: Karl Kleinpaste In-reply-to: on 20 Nov 1998 09:25:18 EST. Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:18990 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:18990 Karl Kleinpaste : > My first guess would have been that your server has decided it doesn't > like multiple connections from one host (hence async retrieval is > failing, on inability to open 2nd connection), but there's no reason > for that to have taken a toll on you just with the latest version. well, yes, there is. I sent lars a patch that will wait for the async connection to finish fetching its article if it thinks it's in middle of fetching the article, rather than requesting it again (which would mean 2x the suckage.) but it doesn't recover if the async connection hangs forever. which is what I suspect is happening. will poke at it a bit. --