Elsewhere I think Mike Lacey has recommended the wait command - you might like to do a search of this forum for his advice on this. However, the bottom line is that these processes do nothing more than take up a slot in the process table and they shouldn't be impacting your system's performance that badly. As long as you can live with this, and there aren't positively hundreds of the things, you may as well wait 'till your next scheduled reboot to kill them. HTH.
yep - you can just leave them, unless they are filling up your process table. They're not really processes anymore, just an entry in your process table waiting for the thing that started them to call wait() and pick up their return code. Mike
michael.j.lacey@ntlworld.com
Email welcome if you're in a hurry or something -- but post in tek-tips as well please, and I will post my reply here as well.
before killing any processes, there might be child be processes, so kill it first before killing the parent, if not the the processes might hang and appear to be there.
The PPID (Parent Process ID) of a Zombie process will be 1, which is part of the operating system, which will *NOT* react nicely to being sent a SIG_KILL with a kill -9 command - so please don't do this at home anyone. But yes <wry smile> as it will get rid of *all* processes (very quickly) on the box, any Zombies will disappear as well! Mike
michael.j.lacey@ntlworld.com
Email welcome if you're in a hurry or something -- but post in tek-tips as well please, and I will post my reply here as well.
yep <grin> and I guessed, from what you'd written earlier, that you wouldn't do such a thing - but lots of people will read this thread
No offence meant Mike
michael.j.lacey@ntlworld.com
Email welcome if you're in a hurry or something -- but post in tek-tips as well please, and I will post my reply here as well.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.