suspending processes (kill -STOP)
Stuart Levy
slevy at poincare.geom.umn.edu
Tue Jun 12 14:23:24 AEST 1990
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 at geom.umn.edu
More information about the Comp.sys.sgi
mailing list