From: "Óscar Fuentes" <ofv@wanadoo.es>
To: ding@gnus.org
Subject: Re: Gnus hangs
Date: Fri, 08 May 2015 01:12:15 +0200 [thread overview]
Message-ID: <87k2wkf0ds.fsf@wanadoo.es> (raw)
In-Reply-To: <87oalxt6yf.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> Any advice on how to diagnose this?
>
> The only thing I can think of is something that many of us have
> encountered, which is that long-running connections die or get cut off,
> and Gnus doesn't know it. That can lead to timeouts/hangs when you try
> to re-use a zombie connection.
>
> The nndraft message shouldn't be significant, it's just the last
> operation to successfully complete before the hang began.
>
> "Once every five g's" sounds a little odd for this problem, because most
> of us have it after some network reconnection (after wake from suspend,
> after VPN on/off, etc), but it's the only thing I can think of.
>
> When I suspect I'm going to have the problem, I hit "z" for
> `gnus-group-suspend'. That closes all the servers, so the next refresh
> re-establishes connections.
>
> `gnus-group-suspend' is a little heavy-duty for this: all you'd really
> need is:
>
> (progn
> (gnus-offer-save-summaries)
> (dolist (elem gnus-opened-servers)
> (gnus-close-server (car elem))
> (setcar (cdr elem) 'closed)))
Thanks. I think that the problem sometimes happens when Gnus starts,
which would rule out your hypothesis, but I'm not 100% sure. I'll use
your trick before updating the summary buffer and see if it avoids the
hang.
next prev parent reply other threads:[~2015-05-07 23:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 23:11 Óscar Fuentes
2015-05-07 3:14 ` Eric Abrahamsen
2015-05-07 23:12 ` Óscar Fuentes [this message]
2015-05-08 9:41 ` Igor Sosa Mayor
2015-05-07 8:39 ` Adam Sjøgren
2015-05-07 23:05 ` Óscar Fuentes
-- strict thread matches above, loose matches on Subject: below --
2005-02-08 14:52 gnus hangs Maciej Matysiak
2005-02-08 15:16 ` Ralf Angeli
2005-02-08 15:44 ` Maciej Matysiak
2005-02-08 15:24 ` Vin Shelton
2005-02-08 15:51 ` Adam Sjøgren
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=87k2wkf0ds.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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).