Path: utzoo!utstat!news-server.csri.toronto.edu!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!wuarchive!mailrus!iuvax!news!cartan!ndmath!nstar!larry
From: larry@nstar.uucp (Larry Snyder)
Newsgroups: news.software.b
Subject: Re: cnews inbound batches going into in.coming/bad
Message-ID: <1990Sep26.114528.24670@nstar.uucp>
Date: 26 Sep 90 11:45:28 GMT
References: <1990Sep24.180726.11442@nstar.uucp> <1990Sep25.151613.1979@zoo.toronto.edu>
Organization: Northern Star Communications, Limited
Lines: 28

henry@zoo.toronto.edu (Henry Spencer) writes:

>In article <1990Sep24.180726.11442@nstar.uucp> larry@nstar.uucp (Larry Snyder) writes:
>>... After I updated the sys file - I started getting
>>bad batches (bundles) in in.coming/bad.  These same
>>batches most always will be processed by cnews when moved
>>back into the in.coming directory - any ideas?

>You left out the most important fact:  what, if anything, is showing up
>in errlog to explain those batches?

relaynews: error writing `L', probably the disk filled
relaynews: error writing `L', probably the disk filled
relaynews: error writing `L', probably the disk filled

>There is also a pervasive illusion that re-running a batch and having it
>work fine tells you something.  Wrong.  Since most batches end up in bad
>because of a flaw in a single article, and all articles in the batch will
>be rejected as duplicates when you re-run the batch, re-running it tells
>you *nothing* in general.

the above message is bogus - I have plenty of disk space --

-- 
       Larry Snyder, Northern Star Communications, Notre Dame, IN USA 
 {larry@nstar, uunet!sco!romed!nstar!larry, nstar!larry@ndmath.math.nd.edu}
                     backbone usenet newsfeeds available
         Public Access Unix Site (219) 289-0282 (5 high speed lines)