Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 3/23/84; site cbosgd.UUCP
Path: utzoo!linus!security!genrad!decvax!harpo!ulysses!cbosgd!mark
From: mark@cbosgd.UUCP (Mark Horton)
Newsgroups: net.news.b,net.sources
Subject: Re: news batching with file size limits
Message-ID: <1248@cbosgd.UUCP>
Date: Mon, 9-Apr-84 21:59:25 EST
Article-I.D.: cbosgd.1248
Posted: Mon Apr  9 21:59:25 1984
Date-Received: Wed, 11-Apr-84 01:43:39 EST
References: <821@nsc.UUCP>
Organization: AT&T Bell Laboratories, Columbus
Lines: 26

Here is another way to do it.  This fix is much simpler, although it
doesn't do as much as some of the other fixes.   The problem is that,
if you use =batch, and your neighbor goes down for a few days, you
can get one huge batch, taking hours to transmit, and when they come
back up, it will burp before it can finish one complete transmission.

The fix is to simply move the copy of the file names to a unique filename
each time uux is invoked by crontab.  The spool directories are rearranged
slightly to avoid recompiling uucp, which only permits transfers from
/usr/spool/batch.  So now the sys file F option appends to
/usr/spool/batchnews/sysname instead of /usr/spool/batch/sysname.
The sendbatchednews script moves it to /usr/spool/batch.  A one line
change is also needed to batch, which unstead of truncating the file
(close(creat)), unlinks it.

	Mark
: ' sendbatchednews : transmit news which has been batched'
F=/usr/spool/batchnews
S=/usr/spool/batch
cd $F
for sys in *
do
	mv $F/$sys $S/$sys.$$
	uux -z -gd -r -c $sys!rnews '<' =/usr/lib/news/batch_$S/$sys.$$
done
/usr/lib/uucp/uucico -r1 &