|
XXXstorage Jeff is correct, if the PID's of the defunct processes are constantly changing and the size of the population is not increasing over time, there's nothing to sweat. There's a minor flaw in some bit of coding (possibly not even yours, but at a lower level- such as a missing/corrupted library file) but it's a low resource drain unless they begin to accumulate.
About how "killing a dead parent to free zombies", what you actually are doing is giving the lost child processes an opportunity to finally exit. As long as the zombie believes its parent is still active, it'll wait for it to deallocate its resources. It will intercept the kill command for the parent (since the parent is no longer there to field it), realize that it is orphaned and proceed to finally exit itself.
So, a (temporary) solution to a production server that has a growing population of zombies is a crontab run often enough to keep the zombies from reaching a critical mass, where they would begin to have a noticible negatory impact on the server. If that's needed, I'll look up the code for it for you. But you'd still need someone to go "under the hood" to apply a pernament solution.
__________________
<CENTER><A HREF="http://www.hot-off-bourbon.com/" target="_blank"><IMG SRC="http://www.hot-off-bourbon.com/images/hob-logosmall.jpg" border="0"></A>
<FONT face="Comic Sans MS" SIZE="-1"><I>Mardi Gras, Spring Break, Wet-T, Night Club Action, UpSkirt, Oil Wrestling, Voyeur</I></FONT></CENTER>
|