Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Haines Brown <brownh@hartford-hwp.com>
Subject: Re: gnus runs away
Date: Fri, 27 Sep 2002 20:06:02 GMT	[thread overview]
Message-ID: <pan.2002.09.27.20.05.20.130236.2772@hartford-hwp.com> (raw)
In-Reply-To: <vaf3crvwm8b.fsf@lucy.cs.uni-dortmund.de>

On Fri, 27 Sep 2002 10:17:24 -0400, Kai Großjohann wrote:

> The node "(gnus)Customization" and its subnode have some information
> on speeding Gnus up.  Be sure to read all sections, not just the one
> on slow network connectivity.  Maybe one of them helps.
> 
> kai

Wow, Kai, thanks for the input, but my problem is quite something else
entirely. My gnus does not have a speed problem, but "runs away" in the
sense that it run and runs without managing to get articles and so can't
stop. 

Since pan runs ok, it's not a problem at the server end. I didn't change
configuration (~/.gnus), and so its not that gnus can't poll the server.
The flickering DSL modem lights suggest that either I'm querying the
server without results, or, as seems more likely, the file headers are
downloaded, but not saved or registered as downloaded. I don't know where
to take it from here. No messages in /var/log/messages.

Haines Brown

 


       reply	other threads:[~2002-09-27 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pan.2002.09.27.11.56.33.759541.2772@hartford-hwp.com>
     [not found] ` <vaf3crvwm8b.fsf@lucy.cs.uni-dortmund.de>
2002-09-27 20:06   ` Haines Brown [this message]
     [not found]     ` <ofaikr90.fsf@ID-23066.news.dfncis.de>
2002-09-28 22:27       ` Haines Brown

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=pan.2002.09.27.20.05.20.130236.2772@hartford-hwp.com \
    --to=brownh@hartford-hwp.com \
    /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).