Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!utcsri!uthub!ecf!me!utradio!utmanitou!lsuc!mnetor!seismo!rutgers!clyde!cbosgd!osu-eddie!bgsuvax!herber
From: herber@bgsuvax.UUCP
Newsgroups: news.admin
Subject: Re: why doesn't expire work as it should?
Message-ID: <1053@bgsuvax.UUCP>
Date: Mon, 18-May-87 11:25:13 EDT
Article-I.D.: bgsuvax.1053
Posted: Mon May 18 11:25:13 1987
Date-Received: Fri, 22-May-87 00:38:40 EDT
References: <247@crin.UUCP>
Organization: Bowling Green State University B.G., Oh.
Lines: 28
Summary: /usr/lib/news/history file not updated properly?

In article <247@crin.UUCP>, tombre@crin.UUCP writes:
> 
> Well, it seemed to work, but today I noticed that in comp.sys, there were
> many articles as old as one month. I thought something with the cron
> commands was garbled, so I ran the expire manually. Some articles were
> cleared away, but many remained. I also tried without spaces between e and 7
> ( ... -e7 -v2 ...) without any change.
> 
> Why doesn't expire work properly? We have been running news 2.11 for several
> months now. The version of expire.c is 2.46, date 9/19/86, according to a
> "strings" on /usr/lib/news/expire.

I've seen the same thing under 2.10.n and have tracked it to the articles
not being listed in /usr/lib/news/history.  The expire program looks there
to find the articles to expire, it doesn't just look in /usr/spool/news/*.
I've gotten in the habit of running an 'expire -r' to rebuild the history
file once a month to insure it is in sync with the actual articles in
/usr/spool/news.  I haven't seen the problem under 2.11 but then again,
I'm still rebuilding my history file once a month yet too.

I never did find out why the articles were being removed prematurely
from the history file or discover if they were being placed there at all.

-- 

Steve Herber			CSNET herber@bgsu.edu
Sr. Systems Programmer		UUCP  ...!osu-eddie!bgsuvax!herber
Bowling Green State Univ.