Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!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: 1 Dec 90 00:17:49 GMT References: <1990Nov27.161854.24449@robobar.co.uk> <1990Nov29.144403.12729@robobar.co.uk> Organization: University of Karlsruhe, FRG Lines: 18 In news.software.b, article <1990Nov29.144403.12729@robobar.co.uk>, ronald@robobar.co.uk (Ronald S H Khoo) writes: < urlichs@smurf.sub.org (Matthias Urlichs) writes: < < > Cleanly shutting down a system where there are files named LOCK, and < > LOCKinput, and LOCKbatch, and LOCKmthreads, seems to be a problem... < < Hmm.. Does this mean that we really ought to have STOP, STOPinput, < STOPbatch, STOPmthreads, etc in $NEWSCTL instead rather than lots of < little stop files scattered about the filesystem ? < Actually, one STOP file should suffice because (at least for me, your mileage may vary) the main reason to stop processing is to shut down the system, and then it doesn't make much sense to stop only one of the above. -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/