Re: Yarn 0.91 expire -r bug

Gary H (garyh@sco.COM)
Mon, 01 Jul 1996 13:56:46 -0700

"Carl D. Cravens" <ravenpub@southwind.net> wrote:
|On Fri, 28 Jun 1996 13:42:09 -0400, mtj@iglou.com (Michael Jones) wrote:
|>If this is the case, then it's not a bug, it's the way Chin is
|>handling the newsbase from .9x up (I presume he won't be going back to
|>the old way -- just as well, because I prefer it this way).
|
|I'm curious as to why you prefer it. It takes up disk space that isn't
|being used and (at least on my systems) expires now crawl at a snail's
|pace compared to the speed they used to run at. I haven't seen any
|user-end benefits of the new format. (I'm assuming that it's done
|something useful/timesaving on the programmer side.)
|
|--
|Carl (ravenpub@southwind.net)
|Contentsoftaglinemaysettleduringshipping.

Carl,

I'll tell you why I perfer it. Basically with the new scheme, you are
less likely to run out of disk space because the space has been reserved
for you. What good is it when you import 5 megs worth of stuff, delete
most (not all) of the articles after you read it so you're basically back
down to a small news.dat file, and then reimport another 5 megs worth of
news article. Just keep it at or around 5 megs if that's what you're going
to use.

Lets say you have 6-8 megs on your HD.
The old way, if you expired some articles so that you are down from 5 megs
to 100k news.dat file and you decide to go into netscape that night
to download a 4-5 meg worth of software, then you download your news.zip file,
you'll run out of space! If you don't then you'll run out of space filtering
and/or unpacking these articles.

Gary