The Perl Cookbook p.559 has recipe 16.4 "Reading or Writing to Another Program" where it describes using the pipe at the beginning to write to the program. 
   $pid = open(WRITEME, "| program arguments") or die "Couldn't fork: 
+$!\n";
   print WRITEME "data\n";
   close(WRITEME) or die "Couldn't close: $!\n";

[download]
The only difference I can see is that the Perl Cookbooks example *includes* error handling ("open(...) or die ...")on the open and close - I think that's what you are looking for to tell you if it succeeded or failed.

HTH.

In reply to Re: capturing exit status of a process by hmerrill
in thread capturing exit status of a process by blackrose

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.