[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [leafnode-list] Problem with texpire

Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:

> Stefan Wiens <s.wi@xxxxxxx> writes:
>> To find broken overview lines:
>> find /var/spool/news -name .overview | \
>>         xargs awk -v FS="\t" '{if(NF>9)print FILENAME" "$0}'
> None here[TM].

Not really surprising.

Instead, your WIP-20010605-1 getxoverline() will get SIGSEGV in
tab2spc() should strdup() fail.

>> Does anyone have an idea how to expire groups which have vanished from
>> groupinfo?
> You mean, after a new group list has been fetched which has some groups
> less? Or on other occasions? Knowing not much of texpire's internals: In
> how far is it relevant if the group to expire is listed in groupinfo?

Documented issue, see texpire(8). Groups not in groupinfo are
currently ignored.

>> Descending the entire /var/spool/news tree (except message.id/ etc.)
>> is not advisable; there might be an unknown subdirectory that better
>> should not be touched.
> Well. We could move all leafnode relevant directories and files into
> leaf.node, then the rest of /var/spool/news would be ours to play with.

I'd be "not amused" should texpire ever clean up my site-local
subdirectories under /var/spool/news. That would be too surprising,
even if documented.

As I mentioned, descending TLHs listed in groupinfo should be
feasible; the problem would then be restricted to vanished TLHs.


leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list