Charlie+ said:
snip
There is not a single post in this above n/g as yet!!
C+
The newsreader keeps track of article numbers. If the
server article numbers are in a different range than
the reader knows about, that can result in no articles
being pulled in.
And some newsreaders make this particularly difficult
to deal with, in that unsubscribing and subscribing
again, doesn't cure the problem. There will still be
a lack of new articles pulled in.
Using a packet sniffer, this is the request, and the
response, for the current newsgroup, on my particular
server. Both the number of articles, and the article
numbers, are particular to each news server.
GROUP alt.windows7.general
211 10072 58609 68687 alt.windows7.general\r\n
I can view these in a packet sniffer, because I'm using
port 119 and the traffic is unencrypted. I can view the
plain text protocol used and figure stuff out.
http://www.ietf.org/rfc/rfc3977.txt
Syntax
GROUP group
Responses
211 total_articles low_water_mark high_water_mark group_name
10072 58609 68687 alt.wi...
That's for my server Eternal-September. Now if I look at
my news.rc file, there is a line per newsgroup, and the
line keeps track of which articles are read. Here, all
the articles are read right now. And the highest article,
equals the high_water_mark, so there are no new articles
to pull in.
alt.windows7.general: 1-68687
There is a news.rc file for each server, and in this case
the actual file name is news.eternal-september.org.rc .
If I was not able to pull in articles, I would shut down the
newsreader, and edit the news.rc file, to this...
alt.windows7.general: 1-1
Now, the current high_water_mark, is above what I've read,
so all the articles from 58609 to 68687 should appear.
Start the newsreader after saving that file, check for
new articles, and the articles should come in.
It's a very simple mechanism, and has worked that way for
some time. I've been hand-editing .newsrc files for quite
a few years, and doing the same thing.
When the group has some articles read and some unread, the
syntax of the line looks like this...
microsoft.public.windowsxp.general: 1-116193,116250,116279
But I hardly ever edit a line with the intent of changing
read to unread or vice versa, because that can be done faster
from the newsreader GUI. The only time I'd be editing that
file, is to set it to "1-1" so that articles/headers would
start rolling in.
If the administrator of the news server "renumbers" articles,
which happens occasionally as part of emergency maintenance,
then I might be forced to that kind of editing.
Newsreaders also have other kinds of database files, on
a per-newsgroup basis. If you have any other problems with
a group, you can try moving or deleting those, and allowing
the newsreader to build new ones. You can do a "mark all read"
if you want to only start looking at new articles.
The view on my newsreader, is set to show both read and unread
articles. Some people have their newsreader set such that
only unread headers are visible in the pane, which makes it
harder sometimes, to tell what's going on. But that wouldn't
stop your efforts to see new articles right now. Just
your ability to see the "history" of the group.
Paul