Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!esquire!yost
From: yost@esquire.UUCP (David A. Yost)
Newsgroups: news.admin
Subject: Re: Cnews wish
Summary: too bad
Message-ID: <1403@esquire.UUCP>
Date: 13 Sep 89 13:30:53 GMT
References: <1401@esquire.UUCP> <1989Sep12.230820.2296@utzoo.uucp>
Reply-To: yost@esquire.UUCP (David A. Yost)
Organization: DP&W, New York, NY
Lines: 24

In article <1989Sep12.230820.2296@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>Well, this may half-please you. :-)  It's not set up that way out of the
>box.  But at least part of it -- expiry only on space shortage -- can be
>done by minor changes to shell files.  People have done it.  We don't
>have a "remove list" or anything like that, but you could get much the
>same effect by doing iterative expiry, generating expire control files
>specifying successively tighter expiry times until you had enough free
>space to suit you.  The overhead needn't be very high if it's managed
>intelligently.  Again, we don't provide the solution, but I think most
>of the tools are there to build your own.

Too bad.  I was hoping for something automatic,
out of the box.  One of the worst things about
Bnews is the amount of nursing it needs, and the
amount of gory detail you need to know about it.

One thing I'm not clear on: using your suggested
fix, does inews make room for itself as it goes
along, or do I still have to guess how much
room to leave for tonight's feed?

 --dave

P.S.  Yup, "expiry" is in my dictionary.