I rely heaviliy on the CommandLine info I get back from WMI, since I know what I started and with which arguments. That might work here.

It would at best be a heuristic. Ie. an informed guess. For exampe, if he needed to run two copies of the daemon concurrently, there would be no way to distinguish between the essentially identical processes started by the two copies. It is also a very expensive way to allow him to continue to use fork.

In this case I was thinking about using the real pid you said came from the forking open and identifying my own from chaining real pid to real ppid.

Once he moves away from using fork and starts using some other mechanism that gives him the real pids--the two I mentioned, or even Win32::Process::Create() etc.--then he will already have a list of real process IDs and can use kill to kill them, so there is no need for WMI or Win32::Process::KillProcess().

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^6: killing on win32 by BrowserUk
in thread killing on win32 by Razvanica

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.