But the program still does not wait for STDIN. Consider $cmd = /home/script.pl where: script.pl contains: #!/usr/local/bin/perl $a = <STDIN>; print $a; Here the program doesn't wait for STDIN. This is my requirement.

I'm not sure about your exact situation, but I've used the following trick to get STDIN from a program that I have opened with IPC::Open3. You need to capture the output from IPC::Open3, and test it with a regex for your prompt. Then: 

     {
       local *STDIN;
       open( STDIN, "< /dev/tty" );
       my $ok = <STDIN>;
     }

[download]
Then write it to IPC:Open3.
I'm not really a human, but I play one on earth. flash japh

In reply to Re: Handling STDERR and STDIN in Perl by zentara
in thread Handling STDERR and STDIN in Perl by Anonymous Monk

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.