Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!uunet!netagw!bill
From: bill@netagw.uu.net (Bill Aten)
Newsgroups: news.newusers.questions
Subject: Re: news.announce.newusers (was Re: Reader polls)
Summary: expire with exceptions
Keywords: expire exceptions
Message-ID: <246@netagw.uu.net>
Date: 12 Nov 89 15:25:00 GMT
References: <8911091544.AA21726@thep.lu.se> <1989Nov9.191236.23264@agate.berkeley.edu> <351@crabcake> <110@toaster.SFSU.EDU> <353@crabcake> <3032@splut.conmicro.com>
Reply-To: bill@netagw.uu.net (Bill Aten)
Distribution: usa
Organization: Computerizers, Inc., Germantown, MD
Lines: 18

>
>Right. All it takes is a line in crontab:
>0 2 * * * /usr/lib/news/expire -e2 -i
>
>Until I get news 3.0 running here, or figure out a way to expire
>news.announce.newusers under different rules than all other groups
>without running expire twice, it'll stay that way, too.

You might give use the following crontab entry instead:
0 2 * * * /usr/lib/news/expire -n !news.announce.newusers -e2 -i

One run of 'expire', but it doesn't touch 'news.announce.newusers'.

-- 
=============================================================================
Bill Aten                             |   Internet:  bill@netagw.uu.net
UUCP:  ...!uunet!netagw!bill          | Compuserve:  70270.451@compuserve.com
=============================================================================