[news.software.b] why doesn't expire work on news.* ?

mkhaw@teknowledge-vaxc.ARPA (Michael Khaw) (05/10/87)

My crontab entry on my Ultrix system for expire is

	0 3 * * * /usr/lib/news/expire -i -n ba ca comp junk \
	  misc mod msgs net news rec sci soc talk

(line-break added for readability, it's actually just one line).

Is there something sacred about articles in news.* that keeps them from
being expired?  We are running B news 2.11:  the "v" command in readnews
just says "B 2.11", no patchlevel shown.

Mike Khaw
-- 
internet:  mkhaw@teknowledge-vaxc.arpa
usenet:	   {hplabs|sun|ucbvax|decwrl|sri-unix}!mkhaw%teknowledge-vaxc.arpa
USnail:	   Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303

fair@ucbarpa.Berkeley.EDU.UUCP (05/13/87)

In article <12600@teknowledge-vaxc.ARPA> mkhaw@teknowledge-vaxc.ARPA (Michael Khaw) writes:
>My crontab entry on my Ultrix system for expire is
>
>	0 3 * * * /usr/lib/news/expire -i -n ba ca comp junk \
>	  misc mod msgs net news rec sci soc talk

the last time I had to set things up on a system that wanted to do
archiving with expire, I found with some testing that the newsgroups
list have to be

	1. separated by commas
	2. one argument on the command line

Thus giving:

0 3 * * * /usr/lib/news/expire -i -n ba,ca,comp,junk,misc,mod,msgs,net,news,rec,sci,soc,talk

Incidentally, this is consistent with argument processing throughout
netnews...

	Erik E. Fair	ucbvax!fair	fair@ucbarpa.berkeley.edu