Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ptsfa.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!lll-crg!dual!ptsfa!dsp
From: dsp@ptsfa.UUCP (David St. Pierre)
Newsgroups: net.news
Subject: Re: limiting news to certain hours of the day?
Message-ID: <749@ptsfa.UUCP>
Date: Tue, 23-Jul-85 22:51:18 EDT
Article-I.D.: ptsfa.749
Posted: Tue Jul 23 22:51:18 1985
Date-Received: Fri, 26-Jul-85 01:57:28 EDT
References: <726@lsuc.UUCP> <3019@nsc.UUCP>
Reply-To: dsp@ptsfa.UUCP (David St. Pierre-150)
Organization: Pacific Bell, San Francisco
Lines: 27

>In article <726@lsuc.UUCP> dave@lsuc.UUCP (David Sherman) writes:
>>Our system is heavily loaded during office hours and can't
>>handle the additional load of uuxqt/cunbatch/news-unpack/rnews
>>
>>Mark Brader (lsuc!msb) and I have been playing with a shell
>>script which would let us batch incoming news by sending it
>>to (say) /usr/spool/newsbatches/* and running the cunbatches
>>from there at night. Before we actually try this kind of
>>thing, has anyone done it already?

I've been running this way for about 3 months. My "cunbatch" just leaves
the files in .XQTDIR. Starting about 6PM, my cron kicks off the real
cunbatch shell every hour for the rest of the night. This allows evening
transmission to be processed in almost real time.

I've built a trivial locking scheme with the PID in a lockfile. If the
process is still running, the new cunbatch (in this case) just goes away.
Otherwise it updates it and starts off.

I've also put a shell front-end into expire to honor the lockfile.
It doesn't go away but sleeps for a while and tries again.

While we do try to coordinate hours with our upstream neighbor, sometimes
we aren't able to connect in the evening. Having cunbatch/compress/rnews
kick off at about 8 AM was a real bummer for everyone.
-- 
David St. Pierre		{ihnp4,dual,qantel}!ptsfa!dsp