m1edb00@arccs2 (03/22/89)
Has anybody run into a problem with Gnews when the
article numbers go over 1000? It seems to lose track of
all the articles less than 1000 whether you've read them
or not. On our system, the number of articles in
comp.emacs just went over 1000 and here's what I found:
The corresponding line in my .gnewsrc correctly shows the
range of emacs articles that I have read:
("comp.emacs" t (1 . 995))
In the comp.emacs spool directory (we're not using nntp)
there are articles from 629 to 1013, and the active file (that
tracks available articles) correctly shows:
comp.emacs 01013 00629 y
Now when I go into gnews and it proffers up comp.emacs I get:
comp.emacs {14} [ynp] ?
It should be:
comp.emacs {18} [ynp] ?
Then when I start reading the articles, the status line shows:
--- Gnews: comp.emacs 1000/1013
It should be:
--- Gnews: comp.emacs 996/1013
Gnews seems to think that the lowest available article is
1000... when I try to force it to show article 999 it says:
article 999 is out of range (1000-1013).
Incidently, this may have happened when we hit 100
and I just didn't notice. And if that theory's true,
the bug won't surface again for comp.emacs until we
hit 10000...?
Could it be some problem that exists only for Gnews
running in spool (non-nntp) mode?
We're running Gnews 2.0 (with patches) on a Sun with
BSD UNIX 4.2 (Sun OS 3.5).
Eric Boutilier UUCP: uunet!fed!m1edb00
(202) 452-2734 INTERNET: m1edb00@fed.frb.gov