Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: news.software.b Subject: Re: C News: batchrunning (on|off) perhaps ? Message-ID: Date: 28 Nov 90 11:32:00 GMT References: <1990Nov27.161854.24449@robobar.co.uk> Organization: University of Karlsruhe, FRG Lines: 27 In news.software.b, article <1990Nov27.161854.24449@robobar.co.uk>, ronald@robobar.co.uk (Ronald S H Khoo) writes: < Anyone else feel the need for such a beast besides me ? < After all, if you're feeding a number of sites, < batchrunning can be just as loading as newsrunning, and sometimes < one does feel the need to stop it :-) < You might want to put checks for the "stop" file into your sendbatches script at some strategic locations. Cleanly shutting down a system where there are files named LOCK, and LOCKinput, and LOCKbatch, and LOCKmthreads, seems to be a problem... especially because th chance that you catch all of them not being present approaches zero with increasing news volume. < Or should I just add "echo $$ > $NEWSCTL/sendbatches.pid" to sendbatches < and kill `cat $NEWSCTL/sendbatches.pid` ? This could only result in one duplicate batch, and therefore seems to be safe. Killing (or crashing a machine with) a running "relaynews" or mthreads seems to be more critical. Does the dbz database have a flag to indicate that the database has been closed cleanly? If not, it should probably be added..? -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/