From: Rob Browning <rlb@defaultvalue.org>
Cc: ding@gnus.org
Subject: Re: Weird infinite (?) loop when entering newsgroup
Date: Sat, 26 Jun 2004 18:47:30 -0500 [thread overview]
Message-ID: <87k6xtnap9.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <un02snt4n.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Thu, 24 Jun 2004 23:44:56 -0500")
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> The problem is that your server sent some garbage that is now
> confusing the agent. One, or more, of your article numbers is
> currently so large that it overflows the emacs integer variable.
>
> Your fix is to edit the .overview file for the group having the
> problem. The first number on each line is the article number. Look
> for lines whose article numbers are not consistent with the rest of
> the file. Most times when this problem has been reported, the article
> number has been duplicated (that is, you have 123456123456 when the
> correct number was 123456). Just delete the problem lines then save
> the file. You should now be able to enter the group and, when you do,
> the agent will re-fetch the headers that you just deleted.
OK, I tried that using a regexp replace, and after removing all the
1234512345 style lines, I was able to enter the group successfully,
but only once. The next time I tried to re-enter the group after
that, the problem returned.
In any case, thanks for the help.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
prev parent reply other threads:[~2004-06-26 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 22:24 Miles Bader
2004-05-21 23:21 ` Kevin Greiner
2004-05-22 2:00 ` Miles Bader
2004-06-24 20:57 ` Rob Browning
2004-06-25 4:44 ` Kevin Greiner
2004-06-26 23:47 ` Rob Browning [this message]
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=87k6xtnap9.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).