Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!POLY1.NIST.GOV!rbriber
From: rbriber@POLY1.NIST.GOV
Newsgroups: comp.sys.sgi
Subject: batch control
Message-ID: <9102031532.AA15085@poly1.nist.gov>
Date: 3 Feb 91 15:32:09 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26


Sometime ago there was a discussion of a batch process control utility which
allowed the user more control over batch jobs.  I con't remember the name of
this utility or whether anyone had successfully built it under Irix.  We 
were wondering if it would solve our problem.  Our users would like to be  
able to start a job in the background and then logoff (or close the window
that started the job on the graphics console) and then at some later time,
log back in and reset the priorities of that job (for example, stop it 
temporarily and the start it back up).  It seems that once you close the shell
that started a given job the only communication you can have with that job
(from another session) is to kill it.  We talked to the hotline about being
able to temporarily stop and then restart the job from another window
and then restart it (sort of like ^z and then %% from the parent window) but
it doesn't seem possible.  We have a 4D80GT running 3.3.1.

Anyone have any suggestions?


 ------------------------------------------------------------------------
| Adios Amebas,         | "I've tried and tried and I'm still mystified, |
| Rob Briber            |  I can't do it anymore and I'm not satisfied"  |
| NIST 224/B210         |                           -Elvis               |
| Gaithersburg, MD 20899|  rbriber@poly1.nist.gov   (Internet)           |
| (301) 975-6775 (voice)|  rbriber@enh.nist.gov     (Internet)           |
| (301) 975-2128 (fax)  |  rbriber@nbsenh.bitnet    (Bitnet)             |
 ------------------------------------------------------------------------