From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Freeze up on general news scan (g)
Date: Mon, 07 Oct 2013 08:59:44 +0800 [thread overview]
Message-ID: <87r4bxrj3z.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871u3y1e0a.fsf@newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>>> For some time now I've been having a problem where when I do a general
>>> news scan (g) It doesn't ever finish. It doesn't always happen and
>>> has been a bit of problem getting a backtrace but finally got one
>>> posted below.
>>
>> I've now added further sanity checking to the async nntp retrieval
>> stuff. Does this fix this problem for you?
>
> I realize this is an old old thread... but I'm still having the
> problem and have had all this time. I've gotten so used to working
> around it that I kind of quit fussing with it... until, lately when I
> posted about it again and got some help from Katsumi, that seemed at
> first to fix things: It was some old code I had kicking around that
> was from way back with this post I'm responding to, was current.
>
> See the thread if interested:
> http://thread.gmane.org/gmane.emacs.gnus.general/83778
>
> Or from gnus:
> Message-ID: <871u4cwiwu.fsf@newsguy.com>
>
> I've ditched that old code of mine, and after a few refreshes I'm back
> to having huge (never ending) waits when pressing 'g'. All nnml:
> nnimap: etc gets refreshed , the last being nnfolder... but when it
> hits the part where it nntp refresh...happens, it just never finishes.
>
> I doubt it is a server problem since any single newsgroup or any nntp
> server refreshes in a normal amount of time... I run in topics so if I
> hit M-g on all gmane groups, good refresh time. Ditto for newsguy.com
> and apn (forte-agent news service)
>
> It only the over all 'g' refresh that goes into infinity.
A "me too" might not be that helpful, but... me too. Any time I resume
the computer or re-connect to a network I'm in the habit of opening a
single nntp group, to prod the connection into life, then hitting 'g'.
next prev parent reply other threads:[~2013-10-07 0:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 17:18 Harry Putnam
2012-01-03 23:17 ` Lars Magne Ingebrigtsen
2012-01-04 15:57 ` Harry Putnam
2012-01-06 14:33 ` Harry Putnam
2012-01-06 21:34 ` Lars Magne Ingebrigtsen
2013-10-06 17:54 ` Harry Putnam
2013-10-07 0:59 ` Eric Abrahamsen [this message]
2013-11-03 11:18 ` Ted Zlatanov
2013-11-04 2:15 ` Eric Abrahamsen
2013-11-04 16:47 ` Ted Zlatanov
2013-11-05 2:59 ` Eric Abrahamsen
2013-11-05 6:03 ` Vincent Bernat
2013-11-11 15:40 ` Ted Zlatanov
2013-11-08 17:58 ` Harry Putnam
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=87r4bxrj3z.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).