-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to B. S. on 10/6/2006 2:48 AM: > For each process there are 4-5 threads, one in state Wait::Executive and > others in Wait::UserRequest (according to Process Explorer). > > Have you got any idea what goes wrong?
This seems to be a repeatedly reported problem, but not one which anyone who is capable of patching has been able to reproduce. One idea is to check whether you have some rogue driver (antivirus or webcam tend to be culprits) that interferes with cygwin in such a way that it triggers these defunct processes, and disabling the driver might clean things up. > > (On top of this writing an automatic script to regularly clean up zombie > processes is not straightforward since ps returns process IDs which are > not accepted by kill...) Try '/bin/kill -f' to use Windows process killing instead of cygwin (yes, you are right that cygwin can't kill a cygwin process if it has locked up in a defunct state). - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFJkbK84KuGfSFAYARAn31AKCnmGoOdGqrn0C9TEIXCgA7IlaimQCgyiJ9 /zsfNhpjiKdSct3evYEQZqg= =wP2w -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
