From: Felix Lee <flee@teleport.com>
Cc: ding@gnus.org
Subject: Re: Pterodactyl Gnus v0.52 is released
Date: Fri, 20 Nov 1998 06:59:14 -0800 [thread overview]
Message-ID: <199811201459.JAA10484@sclp3.sclp.com> (raw)
In-Reply-To: <vxkk90qwiep.fsf@beaver.jprc.com> on 20 Nov 1998 09:25:18 EST.
Karl Kleinpaste <karl@justresearch.com>:
> 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.
--
next prev parent reply other threads:[~1998-11-20 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-20 4:31 Lars Magne Ingebrigtsen
1998-11-20 8:49 ` Graham Murray
1998-11-20 10:52 ` Graham Murray
1998-11-20 14:25 ` Karl Kleinpaste
1998-11-20 14:59 ` Felix Lee [this message]
1998-11-20 15:25 ` Lars Magne Ingebrigtsen
1998-11-20 15:30 ` Graham Murray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199811201459.JAA10484@sclp3.sclp.com \
--to=flee@teleport.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).