From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Cc: 9020@debbugs.gnu.org
Subject: Re: Gnus hanging
Date: Wed, 13 Jul 2011 03:15:21 +0200 [thread overview]
Message-ID: <87tyarq8uu.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <yzaacjmm37.fsf@news.eternal-september.org> (Richard Riley's message of "Tue, 12 Jul 2011 19:43:08 +0200")
Richard Riley <rileyrg@googlemail.com> writes:
> Dave Abrahams <dave@boostpro.com> writes:
>
>> on Wed Jul 06 2011, Richard Riley <rileyrg-AT-googlemail.com> wrote:
>>
>>> I'm frequently on a wireless connection that fails. Gnus hangs if I do a
>>> "g" (or more accurately C-u 5 g) in the group buffer to get new headers
>>> if the link has gone down and come back up again - I assume because of
>>> non valid network stream handles or whatever. What would be the best way
>>> to ensure Gnus closes all network links first and reconnects prior to
>>> the refresh other than quitting or closing/opening from the server
>>> buffer?
>>
>> +1
>>
>> Long-standing issue for me, too.
>
> Any info on this or any ideas how to customise something to restart the
> connections on a "g"? Its hanging all the time on my netbook when the
> wireless is dodgy.
Gnus apparently does re-open the connections when they were closed
(timed out). You can see that when watching them with "netstat -t". Yet
that doesn't seem to help with connections that involve authentication.
So far, I've only found that neither setting nntp-connection-timeout nor
having a deamon like "(gnus-demon-add-handler
'gnus-demon-close-connections 5 nil)" makes any difference.
At the moment, gnus hangs every time I press `g' after it didn't happen
at all for about two days, all for no apparent reason.
It might help to find out what causes the problem if everyone adds their
backtrace[1] to the bug report[2], perhaps with some information added
under what conditions it occurs.
[1]: add "(setq debug-on-quit t)" to your ~/.emacs to get a backtrace
when pressing C-g
[2]: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9020 --- I guess you
can mail additional info by sending it to 9020@debbugs.gnu.org
--
html messages are obsolete
next prev parent reply other threads:[~2011-07-13 1:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 11:04 Richard Riley
2011-07-08 11:14 ` Dave Abrahams
2011-07-08 11:46 ` Antoine Levitt
2011-07-08 12:05 ` lee
2011-07-08 12:54 ` Richard Riley
2011-07-08 16:58 ` lee
2011-07-19 16:22 ` Lars Magne Ingebrigtsen
2011-07-12 17:43 ` Richard Riley
2011-07-13 1:15 ` lee [this message]
2011-07-19 16:20 ` Lars Magne Ingebrigtsen
2011-07-19 17:29 ` lee
2011-07-19 17:30 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1996-07-19 0:13 Gnus v5.2.37 is released Lars Magne Ingebrigtsen
1996-07-19 17:19 ` GNUS hanging Ralph Loader
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=87tyarq8uu.fsf@yun.yagibdah.de \
--to=lee@yun.yagibdah.de \
--cc=9020@debbugs.gnu.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).