I'm trying to figure out how to approach this problem:

I have a server process (on Win2k) that occasionally spikes to 100% cpu utilization and eventually hoses the server if no action is taken. Unfortunately, this process shares its name with 9 other processes so it has been difficult for me to narrow it down. Killing all the processes with the same name is not an option, I need to target only the offending process and kill it.

I've looked into many of win32-process modules and they require the PID to kill it. I then looked into win32-process-perf, but I can't figure out how to get it to look for multiple process with the same name.

To summarize, I'm looking to retreive all PID's from exampleprocess.exe, check CPU utilization and kill the problem process. Any ideas?

In reply to Win32: Multiple processes with the same name by n8wood

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.