Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!amdahl!drivax!news
From: news@drivax.DRI (Wayne Davison)
Newsgroups: news.admin
Subject: Re: junk ->/dev/null
Message-ID: <4393@drivax.DRI>
Date: 14 Mar 89 01:22:58 GMT
References: <1075@bnlux0.bnl.gov> <978@mailrus.cc.umich.edu> <1079@bnlux0.bnl.gov>
Reply-To: davison@drivax.UUCP (Wayne Davison)
Distribution: na
Organization: Digital Research, Inc.
Lines: 25

In article <1079@bnlux0.bnl.gov> abrams@bnlux0.UUCP (The Ancient Programmer) writes:
>	Expire does not allow for something like:
>expire -n junk -e 1 -E 15 -n all -e 15 
>					does it?

No, not unless you modify it, like I did.  I have a ridiculously simple
patch which allows you to specify a separate expire time for each group
or category, as in:

	expire -E 15 -e 15 -n junk:1,talk:7,soc:7,comp.sys.ibm.pc:3,all

This is a very simple modification to the pattern matching subroutine to set
the expire time for each match.  The main body of the code is left unchanged.
Works like a charm, and takes as long as a "normal" expire.

>Two expires, running at the same time does not sound like a great idea.

You betcha, very bad news.  (No pun intended, really :-)  You have to run
them sequentially, using a shell script.  This, of course, takes twice as
long to run.
--
 Wayne Davison                                        ...amdahl!drivax!davison
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
   Lkung tku nrcd pdnm bknwrea xztmykazojb nrcd ypdbd?  Yzt "xztmyk", ypd
   xztmykazoj-nkwdz'b qzrdeg.  Oy o xkjm.bkuzxdb.aojdb ozxprwdz edoz tku.