appstatus & kill & PID

eddymicro · Post by **eddymicro** » Tue Jun 14, 2005 3:15 pm

Alex,

We have a terminal server where a copy of Outlook.exe will hang and we need to kill it. The problem is other copies of Outlook.exe are functioning properly. Can we somehow determine the PID of the bad Outlook.exe and then kill it with the new kill.exe utility. We consider Outlook.exe to be hanging wen it uses the 75-90% of the CPU contineously (although it might still not be "hanging" completley).

Thanks for any ideas on how to do this !

Regards
Ed Schwartz

KS-Soft · Post by **KS-Soft** » Tue Jun 14, 2005 3:35 pm

kill.exe utility provides -h option. This option tells the utility to kill process only when one (or more) windows of the process does not respond to Windows messages.
appstatus.exe utility can be used to monitor such processes.

It doesn't work in your case? Outlook uses 70-90% of CPU and still respond to Windows messages?

Regards
Alex

eddymicro · Post by **eddymicro** » Tue Jun 14, 2005 3:50 pm

Alex,

Thanks for the information. I did not understand how the kill utility knows which instances to terminate. Now I will test and see if it does work.

IF this does not work is their a method to determine the PID of a process that is using the CPU at a certain percentage ?

Thanks,

Regards
Ed Schwartz

KS-Soft · Post by **KS-Soft** » Wed Jun 15, 2005 4:19 am

IF this does not work is their a method to determine the PID of a process that is using the CPU at a certain percentage ?

No, HostMonitor does not provide such option

Regards
Alex