From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Weird infinite (?) loop when entering newsgroup
Date: Thu, 24 Jun 2004 23:44:56 -0500 [thread overview]
Message-ID: <un02snt4n.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <874qp0k721.fsf@trouble.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Miles Bader <miles@gnu.org> writes:
>
>> I've just starting using Gnus 5.10.6 (is this group the appropriate
>> place to post bug reports for older versions?), and when I try to
>> enter the newgroup "comp.emacs", it never seems to succeed, instead
>> printing out an infinite series of messages; I think I've
>> succesfully entered that newsgroup using 5.10.6 before (yesterday
>> :-) though.
>
> For what it's worth, I have the same trouble here when entering
> comp.lang.scheme.
>
> Finding sort keys...
> Sorting records...
> Reordering buffer... Done
> Overview buffer contains garbage ' <xcgisnuy7gd.fsf@mansfield.emba.uvm.edu>'.
> Overview buffer contains garbage ' <3f660e04$0$2839$80265adb@spool.cs.wisc.edu> 5637 111 Xref: intern1.nntp.aus1.giganews.com comp.lang.scheme:44310'.
> Overview buffer contains garbage ' <m3n0ci1a58.fsf@snoopy.treese.org> 17925 326 Xref: intern1.nntp.aus1.giganews.com comp.lang.scheme:45042'.
> Overview buffer contains garbage ' <3f6526a1$0$2840$80265adb@spool.cs.wisc.edu>'.
> Overview buffer contains garbage ' <xcgisnuy7gd.fsf@mansfield.emba.uvm.edu>'.
> Overview buffer contains garbage ' <3f660e04$0$2839$80265adb@spool.cs.wisc.edu> 5637 111 Xref: intern1.nntp.aus1.giganews.com comp.lang.scheme:44310'.
> Overview buffer contains garbage ' <xcgisnuy7gd.fsf@mansfield.emba.uvm.edu>'.
> Overview buffer contains garbage ' <3f660e04$0$2839$80265adb@spool.cs.wisc.edu> 5637 111 Xref: intern1.nntp.aus1.giganews.com comp.lang.scheme:44310'.
> Overview buffer contains garbage ' <m3n0ci1a58.fsf@snoopy.treese.org> 17925 326 Xref: intern1.nntp.aus1.giganews.com comp.lang.scheme:45042'.
> Overview buffer not sorted!
> Finding sort keys...
> Sorting records...
> Reordering buffer... Done
>
> This segment repeats indefinitely.
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.
Kevin
next prev parent reply other threads:[~2004-06-25 4:44 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 [this message]
2004-06-26 23:47 ` Rob Browning
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=un02snt4n.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.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).