Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!sgi!shinobu!odin!bowen@wanda.asd.sgi.com
From: bowen@wanda.asd.sgi.com (Jerre Bowen)
Newsgroups: comp.sys.sgi
Subject: SIGSTOP, job control, and etc.
Keywords: Correction, bug
Message-ID: <11514@odin.corp.sgi.com>
Date: 7 Aug 90 22:22:39 GMT
Sender: news@odin.corp.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 27


spencer@eecs.umich.edu (Spencer W. Thomas) writes:

> Actually, the rules are not nearly as complicated as you imply.  If
> you are not root, you can send signals to any process with the same
> uid.  If you are root, you can send signals to any process.  You can
> send SIGCONT to any process which is a direct descendent of your
> process (in addition to the above rule).

This is correct and stated more clearly than my explanation.

> Process groups have nothing to do with it (unless you use the killpg
> function).

Yep.  You're right.  I'm eating crow.

> If an orphan (a process whose parent is init (process 1)) receives a
> SIGTSTP, it will be killed instead.  However, you can send SIGSTOP to
> an orphan and restart it later with SIGCONT [[Oops -- not true on the
> Iris.  It is true on Suns and 4BSD systems.]]

This is a bug in IRIX and will be fixed in a future release.  Then receipt
of SIG{TSTP,TTIN,TTOU} by a process whose parent is init will kill the
process, but receipt of SIGSTOP by the process will not.

		Jerre Bowen
		bowen@sgi.com