Do you get the output from both print statements? Are you sure that script 2 runs?

At the end of script 1, you use open to execute script 2. This should work, but you don't really check. If you really do need to pipe something to script 2, check the open in script 1:

open(TEST, "|$command") || die "Can't pipe to '$command': $!";

If you do not need to pipe anything to script 2, then system would be a more straight-forward way to do what you're trying to do.

if ( 0 != system( $command ) ) { die "system() exited with status $?"; }

Since your code blocks have an extra unbalanced brace in them, I'm wondering if these are part of a larger program and whether you've actually run the test scripts as you've written them here.


In reply to Re: Child Process and SAMBA by kyle
in thread Child Process and SAMBA by mricci

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.