Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!necis!encore!loverso
From: loverso@encore.UUCP (John LoVerso)
Newsgroups: news.software.b
Subject: Re: Batched ihave/sendme problem
Message-ID: <1857@encore.UUCP>
Date: Mon, 17-Aug-87 10:07:51 EDT
Article-I.D.: encore.1857
Posted: Mon Aug 17 10:07:51 1987
Date-Received: Tue, 18-Aug-87 06:01:06 EDT
References: >2967@b-tech.UUCP<
Reply-To: loverso@encore.UUCP (John LoVerso)
Organization: Encore Computer Corp., Wellesley Hills, MA
Lines: 22
Keywords: runt batches

In article <2967@b-tech.UUCP> zeeff@b-tech.UUCP (Jon Zeeff) writes:
> It appears that under the right circumstances sendbatch will send many 
> ihave messages with only one or two articles listed (in which case it 
> might as well send the article).  
> 
> My solution was to create different scripts for ihaves and articles.  The
> ihave one doesn't loop.

That doesn't necessarilty solve the problem, as sendbatch will do the
same thing for regular batching - i.e, if you run sendbatch at 10 mins
after the hour, and news is unbatching at the time, its likely that
you might get serveral runt batches in a row.

The loop in sendbatch is good (at least for normal batching).  If you've
got a large batch file, it might take a long time to empty it if you
only batch once an hour.  However, it makes it much easier to fill a
disk.  Anyway, the only solution to this would be to add a check in
sendbatch to test for two runt batches (smaller than the size specified
to batch) in a row, and exit w/o error if such occurs.  It might also
be nice to teach sendbatch about disk space hassles, but ...

../John