Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!texbell!uudell!natinst!rpp386!puzzle!news
From: news@puzzle.UUCP (newshound)
Newsgroups: news.software.b
Subject: Re: B News trials and tribulations...
Summary: Is $SPOOLDIR/.tmp there?
Keywords: configure news bnews spool
Message-ID: <46@puzzle.UUCP>
Date: 27 Dec 89 05:01:56 GMT
References: <259@limbo.Intuitive.Com>
Reply-To: bei@puzzle.UUCP (Bob Izenberg)
Followup-To: news.software.b
Distribution: na
Organization: Somewhere in Austin, Texas
Lines: 21
Sender:

In article <259@limbo.Intuitive.Com> taylor@limbo.Intuitive.Com (Dave Taylor) writes:
>Now, first off, what are the files in the ".rnews" directory as used by 
>the "rnews" program?  If there are lots of 'em sitting around, as shown in
>the following listing, is there some way I can force "rnews" to process
>them, or should I just be deleting them to save disk space?

They're article batches that haven't been unbatched yet.  You can run rnews -U
until they're gone, or rnews -S < 89???????????? on each one.

>The third problem is that articles that are "spooled up for later processing"
>in fact just vanish completely from the system.  Where does "inews"
>typically expect to put things, and how are they processed later?

Do you have a /usr/spool/news/.tmp directory?  Can the general public write
into /tmp?
To get those (spooled for later processing) articles taken care of, have news,
through cron, run rnews -U at least once a day, preferably when expire has no
chance of running.
Good luck!
-- Bob
(attctc!puzzle!bei)