Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!umeecs!zip!spencer From: spencer@eecs.umich.edu (Spencer W. Thomas) Newsgroups: comp.sys.sgi Subject: Re: SIGSTOP and SIGCONT rules Message-ID: Date: 28 Jul 90 04:25:51 GMT References: <11074@odin.corp.sgi.com> Sender: news@zip.eecs.umich.edu Organization: University of Michigan EECS Dept Lines: 17 In-reply-to: bowen@wanda.asd.sgi.com's message of 28 Jul 90 00:52:43 GMT 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). 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.]] Process groups have nothing to do with it (unless you use the killpg function). -- =Spencer W. Thomas EECS Dept, U of Michigan, Ann Arbor, MI 48109 spencer@eecs.umich.edu 313-936-2616 (8-6 E[SD]T M-F)