Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!hoptoad!gnu
From: gnu@hoptoad.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: System V job control idea
Message-ID: <2245@hoptoad.uucp>
Date: Thu, 4-Jun-87 05:16:23 EDT
Article-I.D.: hoptoad.2245
Posted: Thu Jun  4 05:16:23 1987
Date-Received: Sat, 6-Jun-87 06:18:25 EDT
References: <337@tdi2.UUCP> <757@mcgill-vision.UUCP> <165@elan.UUCP> <1662@munnari.oz>
Organization: Nebula Consultants in San Francisco
Lines: 13

In article <1662@munnari.oz>, kre@munnari.oz (Robert Elz) writes:
> If you have job control, a suitably authorised user (ie: root)
> can pick a random process and stop it, to be continued later.

I wish this was true.  Trouble is, the parent of that process will
receive a report that it has stopped.  If the parent is a csh, there is
no problem; but if the parent is init, or a Bourne shell, I have seen
it end up killing the job that I had stopped.  I never ended up poking
around enough to find out why.  (This on various versions of SunOS.)
-- 
Copyright 1987 John Gilmore; you may redistribute only if your recipients may.
(This is an effort to bend Stargate to work with Usenet, not against it.)
{sun,ptsfa,lll-crg,ihnp4,ucbvax}!hoptoad!gnu	       gnu@ingres.berkeley.edu