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*

4
  • 1
    disown just removes a given child from a shell's internal list of child processes. The child's PPID remains that of the shell. The shell has forgotten that it ever started that child, but the kernel remembers. Commented Apr 2, 2015 at 22:55
  • Does the process remember its parent? Commented Apr 2, 2015 at 23:21
  • If it wants to know, it calls getppid(2), a system call, and system calls are handled by the kernel. A program could be confused by issuing that call, saving the value, and then using that value after its parentage has changed. There is a chance of a race condition here. Commented Apr 2, 2015 at 23:52
  • Sounds like an interesting new kernel feature. Commented Jul 8, 2017 at 0:57