Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!brazeau.ucs.ualberta.ca!unixg.ubc.ca!ubc-cs!uw-beaver!zephyr.ens.tek.com!uunet!alembic!csu
From: csu@alembic.acs.com (Dave Mack)
Newsgroups: news.software.b
Subject: Re: C News batcher goes insane - film at eleven
Message-ID: <1991Jun28.182345.5627@alembic.acs.com>
Date: 28 Jun 91 18:23:45 GMT
References: <1991Jun26.035746.14008@alembic.acs.com> <1991Jun27.153255.18008@sci34hub.sci.com>
Organization: Alembic Computer Services, McLean VA
Lines: 28

In article <1991Jun27.153255.18008@sci34hub.sci.com> gary@sci34hub.sci.com (Gary Heston) writes:
>In article <1991Jun26.035746.14008@alembic.acs.com> csu@alembic.acs.com (Dave Mack) writes:
>=Twice now, I've run into a situation where the C News batcher
>=manages to produce news batches containing no news. 
>= [ description deleted ]
>=In order to clear this, I either up the batch size and force
>=a more frequent poll from the calling site, or to nuke the togo
>=lists and start over.
>
>If you want the site to get the news, run sendbatches daily. The
>batches will then be built, and sit in your uucp spool directory,
>where expire will neither know or care about them. Whenever your
>downstream site bothers to call, it'll be waiting.

Nope, sendbatches calls queuelen to check the uucp queue. If you have more
than the number of batches specified in batchparms awaiting
transmission, no more batches are created. So you end up with
20+ batches of valid news sitting in your uucp queue, a continuously
growing list of articles in out.going/sitename, and the articles
referenced in that list being expired out from under it. The remote
site calls in for news, gets its chunk of valid articles, then the
batcher starts creating the empty batches.

Someone sent me a patch to batchsplit that may solve this problem.
I'll let you know after I try it out.

-- 
Dave Mack