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.

5
  • Awesome awesome awesome. One follow up: if process 1 spawns 2 and 2 spawns 3 and 2 dies (because it's poorly written), does 3 get re-parented to 1 or does it then have a dangling parent? If the latter, I can always work-around in the 90% case by having a watchdog keep track of the lineage tree, but it'd be great if I could just get that information at the end.
    – iAdjunct
    Commented Jun 9, 2016 at 13:53
  • Also, you saved me from getting another tumbleweed badge. Thank you?
    – iAdjunct
    Commented Jun 9, 2016 at 13:53
  • Ok, doesn't work if 2 is killed, so I guess I'll have to use a watchdog script. Thank you!
    – iAdjunct
    Commented Jun 9, 2016 at 15:09
  • If the parent dies the child pid will get "reparented" to PID 1, so as you've seen this approach isn't sufficient. If you create pid files when spawning the children the watchdog cleanup might be become really simple. See xarg.org/2009/10/write-a-pid-file-in-bash
    – Argonauts
    Commented Jun 9, 2016 at 16:30
  • 1
    You can easily identify orphaned processes and their original ppids (maybe stored along with the pid in each childs pid file) and kill anything that now has a ppid of 1. There's more to it corner case wise, but should be painless.
    – Argonauts
    Commented Jun 9, 2016 at 16:34