🚀 go-pugleaf

In <kherron.667759870@s.ms.uky.edu> kherron@ms.uky.edu (Kenneth Herron) writes:

>emv@ox.com (Ed Vielmetti) writes:

>>    HELP!  My news partition is filling up fast.  Could it be due to all of
>>   those Jan 30th articles that have suddenly started coming in?

>>I would recommend strongly that the next C news patch have an
>>(optional) means of discarding news that is too old.

>We're running news on a 26-processor sequent.  This machine is generally
>I/O bound; it's load average rarely gets above 0.8.  I would gladly trade
>a bit of performance for improved old-article rejection, especially since
>it would be "only" CPU time.

>On the other hand, I'm keeping 38 days of message ID's, so I haven't seen
>many old articles either.

I was only keeping about three weeks worth of old history lines, which
I've now upped to a little over four weeks, and while that may make
some difference, it won't fix the problem because a good share of
these reposted articles have different message ID's than the original
artical.  It looks as if some site out there is modifying the message
ID's and then reposting them.  It is causing much distress to my
server, and most of the sites that I feed.  Does anyone know of a way
to easily go through and expire any article that has a date older than
X, not just expire articles which arrived more than X days ago?
--
"I wrote a lisp program once...it wrote back to me." -- unknown
Reality is for people who can't deal with drugs.
Brett McCoy			Computing and Telecommunications Activities
brtmac@maverick.ksu.ksu.edu	Kansas State University