Path: utzoo!attcan!uunet!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!samsung!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!poincare.geom.umn.edu!slevy
From: slevy@poincare.geom.umn.edu (Stuart Levy)
Newsgroups: comp.sys.sgi
Subject: Re: suspending processes (kill -STOP)
Summary: init bug?
Message-ID: <1990Jun12.042324.16785@cs.umn.edu>
Date: 12 Jun 90 04:23:24 GMT
References: <JIM.90Jun10225458@baroque.Stanford.EDU>
Sender: news@cs.umn.edu (News administrator)
Reply-To: slevy@geom.umn.edu (Stuart Levy)
Organization: Geometry Group, University of Minnesota
Lines: 9

I'd like to know why this happens, too -- why SIGSTOPping a disconnected
process causes it to die.  It seems a reasonable thing to do, and works on
other systems which support SIGSTOP.  Could it be that /etc/init, finding that
its wait() call returns mentioning a process that it hadn't started,
goes and murders the innocent process?  If so, doesn't that seem like a
bug in init?  If not, what on earth is happening here?

     Stuart Levy, Geometry Group, University of Minnesota
     slevy@geom.umn.edu