I need to portably be able to:

  • Start a process
  • Swallow its output
  • Know if it's still running
  • Kill it
  • Verify that it's dead and gone

    Using fork/exec, kill and waitpid have problems on Windows. IPC::Run and IPC::Open3 deal with spawning and I/O, but don't deal with monitoring and control well. Although an attempt with Open3 solved some spawning issues, either waitpid isn't working or the process isn't dying (perhaps due to pending I/O?).

    I searched perlmonks. The link to STEM gives a blank page. POE seems like overkill (I need to be able to justify inclusion of a package into a corporate distribution). Likewise with Parallel::*.

    Are there any portable approaches I haven't considered, tips to make one of the above approaches work, or should I conditionalize my code to use Win32::Process on Windows?


    In reply to Portable Process Management by srvance

    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.