The open method is invoking your Perl script via a shell and that shell's PID is what you get back from the open() call. When you include the ampersand at the end, the invoking shell terminates as soon as it backgrounds process_tar.pl, and so in the course of a few milliseconds at most, the PID you get back from open is no longer running.

Also, if you are interested in the output from process_tar.pl, then you need your open invocation to look like this: 

$pid = open(PID,"$cmd &|") or die $!;

# further on you can read back the output of the command with ...
while ( <PID> )
   {
   echo "PID output: $_\n";
   }

[download]
The way you had it, process_tar.pl was expecting input to be piped to it.

In reply to Re: wrong pid by MonkE
in thread wrong pid by js1

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.