ecarceller
5th January 2007, 17:50
I believe identifying runaway baan processes with 100% accuracy is extremely difficult if not impossible.
However there are things you can do to find suspicious processes at least.
I was wondering what ideas you guys have for this but before asking for them let me share my imperfect system.
This is for UX (gotta think about windows but that will come later)
Check for cumulative cpu time 3 times in a row separated by 2 seconds. If the last 2 checks show cumulative cpu time increase compared to the previous check then it is looking like the process used a cpu 50% of the time or more. As I said it might not mean anything but it is at least suspicious.
The check can be repeated after a sleep of say 2, 3 or maybe 5 minutes. If you have a second hit for the same process then... it is only more suspicious that's all.
Please send your ideas and thoughts.
Thank you very much,
Eduardo
However there are things you can do to find suspicious processes at least.
I was wondering what ideas you guys have for this but before asking for them let me share my imperfect system.
This is for UX (gotta think about windows but that will come later)
Check for cumulative cpu time 3 times in a row separated by 2 seconds. If the last 2 checks show cumulative cpu time increase compared to the previous check then it is looking like the process used a cpu 50% of the time or more. As I said it might not mean anything but it is at least suspicious.
The check can be repeated after a sleep of say 2, 3 or maybe 5 minutes. If you have a second hit for the same process then... it is only more suspicious that's all.
Please send your ideas and thoughts.
Thank you very much,
Eduardo