I have a need to retrieve the handle, (processid) from win32processinfo for vugen.exe, I am not sure how to get it out of the array, this is so i can pass it to another module for monitoring a process. update ..doh a cpan search yields win32 processlist..I can probably use this for the task.. 
use Win32::Process::Info;
use Data::Dumper;
 $pi = Win32::Process::Info->new ();
 $pi->Set (elapsed_in_seconds => 0);    # In clunks, not seconds.
 @pids = $pi->ListPids ();      # Get all known PIDs
 @info = $pi->GetProcInfo ();   # Get the max
 %subs = $pi->Subprocesses ();  # Figure out subprocess relationships.
 @info = grep {$_->{Name} =~ m/vugen/} 
    $pi->GetProcInfo ();        # All processes with 'vugen' in name.
#print $info;
#print $pi;

#my $href=\%subs;
#print Dumper $href;
print Dumper @info;
#print Dumper @pids;

[download]

In reply to access handle from @info using win32 process info by grashoper

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.