Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!rpi!image.soe.clarkson.edu!news
From: nelson@sun.soe.clarkson.edu (Russ Nelson)
Newsgroups: news.software.b
Subject: relaynews failing with status 16
Message-ID: <NELSON.89Jul21223503@sun.clarkson.edu>
Date: 22 Jul 89 02:36:37 GMT
Sender: news@sun.soe.clarkson.edu
Reply-To: nelson@clutx.clarkson.edu
Organization: Clarkson University, Postdam NY
Lines: 15

Sometimes relaynews fails with status 16, which is the value of
ST_DISKFULL, which, of course, is an indication of a disk write error.
It puts the batch into in.coming/bad.  If I move the file(s) out of
bad and then run newsrun, *every* one of the articles is a duplicate.
In other words, a spurious error is being generated after all the
articles have been processed.  I say spurious because we are running
with tens of megabytes free on our spool partition.

Can anyone tell me how to find out *which* call to fulldisk is generating
the error?  I suppose that I could:
	#define fulldisk	dump(__FILE__,__LINE__),fulldisk
but that seems somehow dangerous.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])|(70441.205@compuserve.com)