UNIX Zombies and Daemons -


I understand that when a process is not cleaned then zombie is created (its resources are not retrieved Is / is cut). After calling for the fork () to make a new process, parents should always call waitpid on that process, to clear it.

I have also learned that a child, who was created by himself, fork, and then let the child die, obviously the init process in Unix (Paid # 1) after you do this process Will be detained.

What should I know - as far as I know, when a parent dies, then it becomes clear that the child automatically - so how a zombie is made in the first place ?

Secondly, the guardian of a repressive process stops, why the Damonius process is not considered zombie?

What should I know - as far as I know, when a parent dies If the child goes, the child cleanses himself - how does a zombie become in the first place?

No, parents do not clean children themselves whenever a process ends, all its children (running or zombie) are init process.

The zombies are child processes that have already been eliminated, and their origin is still alive, but so far they do not have to say wait to get the status of their exit. Parents die (and not wait) ), all zombie children are adopted by the init procedure and this will eventually end up with wait To call them all to bite, then they process logic To disappear.

The idea behind placing a zombie process is to keep the appropriate data structure close to the process, through a wait

Secondly, the parent of a blue-print process stops, so why not the demonstrated procedure is considered zombie? setsid system call.

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -