Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!cathyf
From: cathyf@rice.edu (Catherine A. Foulston)
Newsgroups: news.admin
Subject: Re: Left-over .ina & .ara files in SPOOLDIR
Message-ID: <2249@brazos.Rice.edu>
Date: 20 Oct 89 19:04:02 GMT
References: <79@crk56.bnr.com> <716@ecicrl.UUCP>
Reply-To: cathyf@brazos.rice.edu (Catherine A. Foulston)
Organization: Rice University, Houston, Texas
Lines: 45

In article <716@ecicrl.UUCP> clewis@ecicrl.UUCP (Chris Lewis) writes:
>In article <79@crk56.bnr.com> janick@bnr.ca writes:
>
>>I get a bunch of .inaXXXXX and .araXXXXX (where 'XXXXX' is a 5 digit number,
>>looks like mktemp(3) filenames to me) left in the news SPOOLDIR.
>
>>Any idea why ?
>
>What version or patch level of news are you running?
>
>Anyhow, you're in luck this time....  I recognize this bug (this
>should perhaps be in a "monthly news software bug posting" perhaps?) and the
>version.  You are running B-news, probably patch level 14, possibly 13.
>
>This is something to do with cancel messages dropping core by
>walking off the end of a buffer.  Patch 15 repaired this problem, but
>the following two liner will fix *this* problem without having to
>go through doing a patch 15, 16 and 17 upgrade.

	[patch deleted - it consisted of adding two lines.]

>Chris Lewis, Elegant Communications Inc.
>UUCP: {uunet!mnetor, utcsri!utzoo, uunet!attcan!lsuc, yunexus}!ecicrl!clewis

I have a similar thing, but it isn't from cancel dumping core, I don't
think.  I have SPOOLDIR/.tmp which is full of .inaXXXXX and other forms.
There are 8000 of them in there.  They are taking up 50 Meg.  A lot of
them seem to be comp.mail.maps type stuff although not all of them.
I also have .bad, which has ~300K and .rnews which is empty.  What are
these things for?  Especially the .tmp - that is a lot of disk space!  I
cleaned out a whole bunch last time I recompiled news, and they're back
now.

My cancel does dump core, but I have not figured out why.  It never works
from a newsreader and it dumps core when you invoke it directly.  I haven't
had a chance to check the code to see why it doesn't work.  I had
read that a particular combination of option settings would cause it not
to work, but haven't figured out what they are.  

Oh yeah, I am running B 2.11.18 and had these problems when I started
with 2.11.17.  I do have the patch given above already installed.
Any more ideas, anyone?

Cathy
cathyf@rice.edu