|Summary:||Feature Request: new Proc based api isDefunct()|
|Product:||frysk||Reporter:||Phil Muldoon <pmuldoon>|
|Bug Depends on:|
Description Phil Muldoon 2006-07-31 23:20:46 UTC
There seems to be quite some time between when a process is defunct and when it gets cleaned up. In the meantime, the user could ask to do something with this process and causes Frysk to crash, or relay bad or old info. The refresh cycle that Frysk uses can also be long, so it has to be an on-demand read much like getGID and getUID. Does the state in /proc/$$/status get updated in a fairly fast manner? I notice it has Z for zombie as a state in there.
Comment 1 Andrew Cagney 2006-08-01 13:16:09 UTC
Unfortunatly, no matter what we do the race will always be there; when unattached we need to be ready for defunct and/or disappeared errors as responses to an error. A kernel mechanism for informing us when an attached process has gone from defunct to disappeared would be useful.