Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I search on the internet and on the forum. Many suggest when encountering a defunct process, what to do with it is to kill its parent process. However, in the following case it looks like I have to kill the init process. That means to reboot? Or what to do would be better in dealing with such problem?
Processes that die sit in a "zombie" state waiting for their parents to "reap" them. This is done specifically so that the parent can reliably obtain final-status information. If the parents do not do this, a certain (but not unlimited) number of defunct processes can sit around for a while.
If the parent process dies, the children are briefly parented to "init," which will reap them.
"init" is a very special process that cannot die. Don't mess with it.
Don't be alarmed about a certain number of defuncts in the process table. They actually do no real harm.
I have to do this fairly often because Adobe Flash Player is a piece of garbage.
Don't kill the init process!
That is the problem. When I try to kill the its parent process. The parent process dies, but the zombie process then becomes child process of init; and it won't go away if I issue command e.g `kill -9 9993` where 9993 is the zomebie process I want to kill.
Code:
User 9993 7542 0 Apr26 pts/4 00:00:00 /usr/lib/wine/wine-pthread Setup.exe
Code:
$ kill -9 7542
Code:
$ ps -ef | grep wine
Code:
User 9993 1 0 Apr26 ? 00:00:00 /usr/lib/wine/wine-pthread Setup
If I try e.g. kill -9 9993, the command looks works successfully. But when using `ps -ef | grep ...' command, the process is always there. Is there any way I can exactly kill it (though I think kill -9 is the only way I can do)?
Thanks your help.
Last edited by shogun1234; 04-26-2009 at 11:17 AM.
Processes that die sit in a "zombie" state waiting for their parents to "reap" them. This is done specifically so that the parent can reliably obtain final-status information. If the parents do not do this, a certain (but not unlimited) number of defunct processes can sit around for a while.
If the parent process dies, the children are briefly parented to "init," which will reap them.
"init" is a very special process that cannot die. Don't mess with it.
Don't be alarmed about a certain number of defuncts in the process table. They actually do no real harm.
But I saw the CPU usage is increasing. And the sound of my laptop becomes loudly. So we don't actually have any way to get rid of that zombie process?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.