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*

3
  • Thank you for writing this; now I don't have to.    :-)    Processes are like upside-down icebergs: you can easily see the 90% that's above the surface (in userland), but the 10% that's in kernel space is part of the process, too.  I disagree slightly with something you said: "the process is killed right away, [and then] its resources [are] freed, etc."  I would say that the actual, final death of the process doesn't occur until at least when the exit() routine returns control to the scheduler; arguably, not until the parent reaps the status and the proc table entry is freed. Commented Dec 14, 2018 at 4:04
  • @G-Man Hmm, I see what you mean, I've oversimplified that part. It's quite philosophical in a way: are you dead when you cease to be conscious of being alive or when others do? :p Commented Dec 14, 2018 at 9:18
  • Wow; I didn't intend for this to get all Philosophical and Metaphysical!    :-)    ⁠ Commented Dec 14, 2018 at 9:31