Path: utzoo!attcan!uunet!peregrine!ccicpg!cci632!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!rochester!cornell!mailrus!uflorida!novavax!twwells!bill From: bill@twwells.com (T. William Wells) Newsgroups: news.software.b Subject: Re: Comments on C news Message-ID: <1989Jun18.040742.10201@twwells.com> Date: 22 Jul 89 04:07:42 GMT References: <2228@vicom.COM> Organization: None, Ft. Lauderdale, FL Lines: 36 A couple of points: In article <2228@vicom.COM> lmb@vicom.COM (Larry Blair) writes: : The fact that : by default news is always spooled with deferred execution [maybe there's a : good reason for this]. Actually, there's an easy fix for this: look in the input directory of the source and you will find rnews.batch and rnews.immed. Check it out. : Some of the questions in the config are unanswerable : by even an experienced admin [is your rindex fast?]. I had no problem with installation questions, but then again I don't have rindex. : Another thing I noticed is that the spooler won't spool the incoming batch : if space is short. On some systems [ours], /usr/spool/uucp and /usr/spool/ : news are on the same filesystem. This means that spooling the incoming : batch doesn't increase the space used (when the uucp D. file goes away). This is not true. Remember that disk files are allocated in fixed size chunks; for example, using the stats for the feed on my system: block size percent over incoming 512 14 1024 27 2048 51 If you are short on disk space, you may very well want to defer processing the batches. --- Bill { uunet | novavax | ankh | sunvice } !twwells!bill bill@twwells.com