is there anyway to detect whether a process is idle/ready/busy? i've been searching through the API's and WMI docs and still haven't found it. i can get what's running and shut down what i want, but i would like to know if it's busy before i shut it down. anyway to do this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
detecting idle process
- Thread starter bbolte
- Start date
» idle/ready/busy
Windows has no concept of this. I guess you could define "idle" to mean "has no messages in the thread queue", but you can't read another thread's message queue.
You could try using hooks, and tracking when the last time a thread has processed a message. That would provide a fairly good implementation of "idle/busy" for User-Interface threads.
Because worker threads do not usually process messages, you should have the process signal a named event or something when it's busy, so that you can test with WaitForSingleObject with a timeout of zero.
I REALLY hope this helps.
Will
Windows has no concept of this. I guess you could define "idle" to mean "has no messages in the thread queue", but you can't read another thread's message queue.
You could try using hooks, and tracking when the last time a thread has processed a message. That would provide a fairly good implementation of "idle/busy" for User-Interface threads.
Because worker threads do not usually process messages, you should have the process signal a named event or something when it's busy, so that you can test with WaitForSingleObject with a timeout of zero.
I REALLY hope this helps.
Will
- Thread starter
- #4
- Status
