Zombie state courtesy of MS

Log Out | Lost Password? | Topics | Search Contact | Register | My Profile | SO home | MOL home

Thread Originator Last Poster Posts Pages Last Post   Closed: New threads not accepted on this page

Author Message   Earlster Supporter Username: Earlster Post Number: 1274 Registered: 8-2003 Posted on Friday, August 12, 2005 - 3:17 pm:        I'm playing with the latest beta version of their new development environment. Trying to convert a properly closed project to the new format, this is what I get. What's a zombie state anyway?   Tom Reingold Supporter Username: Noglider Post Number: 9062 Registered: 1-2003 Posted on Friday, August 12, 2005 - 3:20 pm:        I don't know about files being in a zombie state, but you can google "zombie process" and learn what it means in unix. I don't know if that applies. Basically, some process ended but it still occupies a slot in the process table. It's benign unless the process table is full. But I suspect that won't help you.   AlleyGater Citizen Username: Alleygater Post Number: 881 Registered: 10-2004 Posted on Friday, August 12, 2005 - 3:29 pm:        a zombie state is what happens to mind every moment I am using a Windows machine.   Earlster Supporter Username: Earlster Post Number: 1275 Registered: 8-2003 Posted on Friday, August 12, 2005 - 3:43 pm:        Tom, thanks for trying to help. I'm merely venting here about useless error messages. This has nothing to do with a UNIX zombie process. It's a configuration file and I assume that they simply have a bug in their code (it is beta after all) that fails to read the file properly. I'm trying to port a project that I started on VS.Net 2003 and I made that stupid decision to continue development on VS.net 2005 beta. It has been a huge waste of time, since they changed so much and there seems to be no binary compatibility, due to lots of changed default settings. I'm frustrated and p'd off. Rant over.   monster Supporter Username: Monster Post Number: 1086 Registered: 7-2002 Posted on Friday, August 12, 2005 - 4:04 pm:        A Zombie State is what happens when you don't use a Mac of course....   Mayor McCheese Supporter Username: Mayor_mccheese Post Number: 465 Registered: 7-2004 Posted on Saturday, August 13, 2005 - 2:12 pm:        Subprocess information shows how many actual subprocesses exist at the time of the report, as indicated by the PID and bolded, non-zero liftime (in minutes). The soft-limit specifies how many CGIplus scripts are allowed to continue existing before the least used is deleted and the hard-limit show how many subprocesses may actually exist at any one time (the margin allows for subprocess deletion latency). A count of how many times the CGIplus subprocesses have been explicitly purged (button available on this report page). The life-time of zombie processes (in minutes, zero implying use of zombies is disabled) and the number that have been purged due to expiry. CGIplus subprocess life-time (in minutes, zero implying indefinite), the number purged due to life-time expiry and the number of CGIplus subprocesses that the server has actually purged (deleted) to maintain the soft-limit margin specified above. Each of the allocated subprocess data structures is listed. There may be zero up to hard-limit items listed here depending on demand for DCL activities and the life of the server. Items with a PID shown indicate an actual subprocess existing. This can be a zombie subprocess or a CGIplus subprocess. If no subprocess is indicated then the other information represents the state the last time the item's associated subprocess completed. Information includes the script (URL-style path) or DCL command, total count of times the item has been used and the last time it was. The zombie count indicates the number of time the same subprocess finished a request and entered the zombie state. The CGIplus column indicates it is/was a CGIplus script and shows the total number of times that particular script has been/was used. If the subprocess is currently in use the client information show the client host name. If any subprocesses are associated with any data structure a purge button is provided that forces all subprocesses to be deleted. This can be useful if a new script image is compiled and it is required all scripts now use this. If a script is currently processing a request the subprocess deletion occurs when that processing is complete. The purge button does not force a subprocess to delete, so a second button forces all subprocesses to delete immediately. This can be used to forceably clear errant scripts, etc., but be warned script processing is indiscrimately stopped! Found at : http://wasd.vsm.com.au/ht_root/doc/htd/htd_1900.html When a child process exits, it is not immediately cleared off the process table. Instead, a signal is sent to its parent process, which needs to acknowledge it's child's death, and only then the child process is completely removed from the system. In the duration before the parent's acknowledgment and after the child's exit, the child process is in a state called "zombie". Found at: http://users.actcom.co.il/~choo/lupg/tutorials/multi-process/multi-process.html I don't know if that will help, but after a quick google search that is the top of the list.   Earlster Supporter Username: Earlster Post Number: 1279 Registered: 8-2003 Posted on Saturday, August 13, 2005 - 9:15 pm:        Thanks, all I figured it out. The file I was trying to convert was 'read-only', because it came out of source control.