From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: nntp hangs
Date: Tue, 06 Mar 2012 17:09:24 +0900 [thread overview]
Message-ID: <b4mk42ytakr.fsf@jpl.org> (raw)
In-Reply-To: <87aa3ug9tc.fsf@geneva.hpsy.me>
Joseph Gay wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>> Like I said there, I thought setting the heartbeat parameter would work
>>> but it doesn't seem to. So maybe it's a Gnus bug?
>> Or a TCP-keepalive bug? I tried commenting out that section in
>> nntp.el. So far Gnus doesn't seem to hang up...
I still have met with hanging up for a couple of times, so TCP-
keepalive is probably not the cause. As I wrote first, Gnus loops
in `nntp-with-open-group-function' at that time. It must mean that
`process-status' said, just before it, that the nntp connection is
open. In the echo area the "Opening nntp server on SERVER...done"
message is shown and is not shown.
>> I suspect Emacs may keep thinking the nntp connection is alive,
>> i.e. `process-status' returns `open', even if the remote news
>> server disconnects it unilaterally.
A workaround for this problem may be:
- Run `nntp-with-open-group-function' with a timer.
- Kill and reopen the connection when a specified time is up.
> This does seem plausible as I've just experienced what appears to be the
> same bug on an ssh connection through TRAMP. The strace reveals a select
> read poll loop where read always returns EAGAIN.
So, it's an Emacs bug? I'm going to try it with XEmacs.
next prev parent reply other threads:[~2012-03-06 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 8:04 Katsumi Yamaoka
2012-03-01 14:39 ` Tassilo Horn
2012-03-02 17:05 ` Ted Zlatanov
2012-03-05 11:10 ` Katsumi Yamaoka
2012-03-05 18:51 ` Joseph Gay
2012-03-06 8:09 ` Katsumi Yamaoka [this message]
2012-03-10 0:37 ` Lars Magne 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=b4mk42ytakr.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).