Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!twwells!bill From: bill@twwells.com (T. William Wells) Newsgroups: news.software.b Subject: Re: CNews building up files in "in.coming" Message-ID: <1989Oct25.023352.8840@twwells.com> Date: 25 Oct 89 02:33:52 GMT References: <1989Oct22.192159.4827@acd4.UUCP> <1989Oct23.023759.17067@utzoo.uucp> Organization: None, Ft. Lauderdale, FL Lines: 33 In article <1989Oct23.023759.17067@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes: : In article <1989Oct22.192159.4827@acd4.UUCP> mjb@acd4.UUCP ( Mike Bryan ) writes: : >I've noticed that when C News is unbatching articles in the in.coming : >directory, it doesn't remove the batch files until it is completely : >done. It seems to me that newsrun should remove each file in turn : >immediately after unbatching the articles it contains... : : If you are running a current C News, it will (a) remove the batch files : after every 50 files processed, or (b) remove the batch file after each : file processed, depending on whether space is tight or not. This was : a deliberate change from our earlier version that always did (b). This really isn't adequate. Because it assumes relatively small batch files. On my system, I get batches of 250K (compressed) and up, and having them accumulate can be a real bear. Especially when disk space gets tight. (Why such big batches? It makes sense if you have a 9600+ BPS modem with built in error correction. Like my Telebit.) Could you either make this based on the file sizes, or provide an option or configuration parameter to make it delete after each batch? Perhaps you could make that 50 a configuration parameter? This behavior has messed me over more than a couple of times. Now that I think about it, I have a feeling that there are several assumptions in C news that are invalid when batch sizes are typically very large. Perhaps you might want to think in terms of a configuration options for these kinds of systems. --- Bill { uunet | novavax | ankh | sunvice } !twwells!bill bill@twwells.com