🚀 go-pugleaf

ted@nowtsfree.freeserve.co.uk (Ted) writes:

[snipppppety]

> My news-reader (xrn) thinks the last article seen was no. 69232, as
> recorded in my ~/.newsrc, so its shown no new articles to me for the last
> day or two.

> I presume leafnode skips a news-group because freeserve offers it crazy
> article numbers. 

Not quite. Leafnode generally puts up a warning about "upstream servers
switched?" when it detects the maximum article # in the parent is suddenly
less than its own, but as it works by Message-ID instead, it seems to work
anyway. (It just drops down to "last initial_fetch combined with max_fetch"
and gets, in my case, no more'n 250 or 150 articles.)

> Why does this happen?  Is it my setup, or freeserve's news-servers?

Probably your end of things. I think you should've had nodesc=1 as a normal
rule - leafnode isn't particularly happy with group descriptions and they
just slow the all-newsgroup download down. Something I snipped above
pointed at nodesc, anyway.

> Is there a fix I should know about?

nodesc=1 and fetchnews -fvvvv once more for good measure, should fix
it. Oh, and remove the ranges in ~/.newsrc, so it just looks like
	uk.comp.os.linux:
with no numbers - you'll have to do a selective catch-up in xrn but that
way you can avoid reading too mcuh, anyway.

~Tim
-- 
| Geek Code: GCS dpu s-:+ a-- C++++ UBLUAVHSC++++ P+++ L++ E--- W+++(--) N++ 
| w--- O- M-- V-- PS PGP++ t--- X+(-) b D+ G e++(*) h++(*) r--- y-	     
| The sun is melting over the hills,         | http://www.glutinous.custard.org
| All our roads are waiting / To be revealed | piglet@glutinous.custard.org