[leafnode-list] Re: re-fetch

[Matthias Andree]

Am 29.08.2012 18:18, schrieb Thufir:
> I set maxage to 0 after:
> 
> tin.users: skipping articles 1-1944 inclusive (initial limit)
> tin.users: considering articles 1945 - 1994
> tin.users: killed 1945 (<E1SJTed-00057J-NJ at akk10-int.akk.uni-
> karlsruhe.de>), too old (136 > 10) days
> 
> It's an initial fetch.  My expire settings:
> 
> root at dur:~# 
> root at dur:~# grep expire /etc/news/leafnode/config
> ## Articles that haven't been read for <expire> days get expired and
> ## removed by texpire(8), unless you define special expire times.
> ## Note that texpire arguments can change this to relate to the date of
> ## arrival. See the texpire manual page.
> expire = 999
> groupexpire gwene.ca.craigslist.vancouver.labour.general = 3
> groupexpire gwene.com.economist = 3
> ## Non-standard expire times (glob(7) wildcard constructs possible)
> # groupexpire comp.os.linux.* = 5
> # groupexpire any.local.newsgroup = 100
> # archive this group (fetchnews uses the global expire to figure the
> # maxage, but texpire will skip it):
> # groupexpire my.archived.group = -1
> ## WARNING: maxage can be overridden by expire! See the clamp_maxage
> ## By default, maxage is limited to groupexpire (if applicable) or
> ## expire (otherwise). On some rare occasions, this limit may be
> root at dur:~# 
> 
> 
> to refetch, just remove from interesting.groups and then resubscribe?

No, you don't, server-side article numbers are tracked in
$SPOOLDIR/leaf.node/$SERVERNAME files (but that can change for leafnode-2).

Instead use  fetchnews -x 12345
to refetch the last 12345 articles per each group.

Oh, and try: man fetchnews :-)

HTH
Matthias