Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Prevent freezing when having bad connection?
Date: Wed, 22 Feb 2012 06:21:43 -0500	[thread overview]
Message-ID: <87wr7f6rlk.fsf@lifelogs.com> (raw)
In-Reply-To: <86zkcb1uys.fsf@web.de>

On Wed, 22 Feb 2012 03:07:55 +0100 Michael Heerdegen <michael_heerdegen@web.de> wrote: 

MH> Lars Ingebrigtsen <larsi@gnus.org> writes:
>> > strace -fp just prints
>> >
>> > [pid 22477] recv(12, 0xb73cfa0, 5, 0) = -1 EAGAIN (Resource
>> > temporarily unavailable)
>> 
>> This is a different problem.  The bug I fixed was related to writing,
>> not reading.

MH> I'll look for the socket when I'm at home again.

MH> BTW, when I got that, I simply pulled out my USB stick, so that the
MH> connection was still active, but with a zera data rate.  I hope that's a
MH> good way to mimic a "bad connection" (or should I better put a metallic
MH> coffee tin around the stick?).

I have noticed hung NNTP connections that manifest the same way.
Usually `C-g' will fix it but it's very annoying because it looks as if
it's waiting for the remote server and you sit for 10-15 seconds before
you realize it's hung.  `strace -p' shows read() returning EAGAIN over
and over.  This is hard to simulate though, I have to open the
connection and wait 10 minutes to be sure it will hang.

Lars, I thought we were setting a heartbeat on the TCP connections in
Emacs?  Is Emacs supposed to notice that the NNTP connection is hung?
This is not encrypted with GnuTLS so I think it's an Emacs-level issue.

Ted




  reply	other threads:[~2012-02-22 11:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 21:00 Michael Heerdegen
2012-02-11 15:32 ` Lars Ingebrigtsen
2012-02-11 19:21 ` Lars Ingebrigtsen
2012-02-17  3:29   ` Michael Heerdegen
2012-02-20  7:33     ` Lars Ingebrigtsen
2012-02-22  2:07       ` Michael Heerdegen
2012-02-22 11:21         ` Ted Zlatanov [this message]
2012-03-10  1:01           ` Lars Magne Ingebrigtsen
2012-03-12 22:57             ` Michael Heerdegen
2012-03-14 14:52               ` Lars Magne Ingebrigtsen
2012-03-12 22:55           ` Michael Heerdegen
2012-03-14 14:53             ` 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=87wr7f6rlk.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).