Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!rutgers!ames!ptsfa!hoptoad!academ!killer!root
From: root@killer.UUCP (Admin)
Newsgroups: news.admin
Subject: Re: why doesn't expire work as it should?
Message-ID: <909@killer.UUCP>
Date: Wed, 20-May-87 11:23:52 EDT
Article-I.D.: killer.909
Posted: Wed May 20 11:23:52 1987
Date-Received: Sun, 24-May-87 03:33:31 EDT
References: <247@crin.UUCP> <802@instable.UUCP> <152@csccat.UUCP>
Organization: The Unix(tm) Connection, Dallas, Texas
Lines: 24
Summary: Bad dates

In article <152@csccat.UUCP>, jack@csccat.UUCP (Jack Hudler) writes:
> In article <802@instable.UUCP>, amos@instable.UUCP (Amos Shapir) writes:
> > I have noticed that when the system is down at midnight on the day
> > an article should have expired and 'expire' didn't run that night,
 
> I have had the same problem, I use to expire on a 14 day schedule but
> reduced it to 7 days and noticed a week later that it did not reduce
> my disc space reqirements. Looked in the spool directory and found
> 1000+ files greater than 7 days old! Not only that but I found a bunch
> of bogus file numbers like 56702,23001...etc.
 
  I have also been looking at this and have found a number of articles
with bad dates - ie - Date: 17 Jul 1988. In addition to Expire: dates of
over three years from now, this date seems to do the same - prevents
expire from removing the article. As I do use the -p option, these are
left around until I check for them. When I do find these, I simply
change the date to that of the timestamp and let expire take care of it
as well as the history files. 
  Other than this, I have found no real problem with expire. The software
is running at patchlevel 8, 3B2/400, Unix SVR2.0.5.


                                           Charlie Boykin
                             {cuae2,ihnp4}!killer!root