From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: Async NNTP code disabled for now
Date: Tue, 15 Feb 2011 13:16:49 -0500 [thread overview]
Message-ID: <m3vd0l2mdy.fsf@jhcloos.com> (raw)
In-Reply-To: <87pqqutgd9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 14 Feb 2011 14:12:50 -0800")
>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
JC> The bug seems to be that with the async code gnus cannot deal with the
JC> other side of an nntp session closing the socket. At least not while
JC> gnus is still on its first iteration through its list of servers.
LI> Right. That sounds likely.
Which means you should be able to replicate it by setting some nntp
server you use to time out idle conenctions after one second or so.
Or maybe after just a few centiseconds?
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2011-02-15 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 18:06 Lars Ingebrigtsen
2011-02-14 21:44 ` James Cloos
2011-02-14 22:12 ` Lars Ingebrigtsen
2011-02-15 18:16 ` James Cloos [this message]
2011-02-18 23:21 ` Lars Ingebrigtsen
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=m3vd0l2mdy.fsf@jhcloos.com \
--to=cloos@jhcloos.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).