Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

18
  • 4
    $\begingroup$ +1 just for the title! $\endgroup$ Commented Jul 30 at 13:08
  • 2
    $\begingroup$ +1 for your user name! XD $\endgroup$ Commented Jul 30 at 13:09
  • 6
    $\begingroup$ Come one, zombie process is a well-defined technical term. $\endgroup$ Commented Jul 30 at 13:43
  • 3
    $\begingroup$ This site is read by students and scholars from innumerable countries and languages, so while I as an English speaker am amused by the title, I'm certain that there are many whose native tonge is Tagalog, or Urdu, or Mandarin, or ... are confused by the title. I would change it. $\endgroup$ Commented Jul 30 at 15:44
  • 2
    $\begingroup$ @b3m2a1 Right, in Unix, a parent doesn't kill its children when it dies. It can trap some signals and kill its children before exiting, but it cannot trap a SIGKILL signal. It can trap SIGSEGV (segmentation fault), though. Proceeding after SIGSEGV seems risky. SIGKILL normally isn't sent; it should be SIGTERM, unless the process ignores SIGTERM. It's possible that the Wolfram Kernel traps these signals (except SIGKILL) and does its own cleanup. Then maybe $Epilog could work. -- Nope, it seems not, using kill.... $\endgroup$ Commented Jul 30 at 19:35