The code has other parts where variables are declared, that's why the posted code is not compiled w/ strict. Actually, i did not mean you will compile it, but rather a look and give me your feedback on possible reason of such pipe behaviour. So, do not look at the strict, or include in the file before your compilation. I publish code pieces as they are, basicly, because of «use POSIX qw( mkfifo )».

Seems to me that using «$|=1» is redundant here. By design, «$FIFO» has to do all the stuff OR «$|» w/o using «IO» module.

Also no need for «\n» in «print $FIFO 'pause'» becuse it works as bad as without it.

I did run your script and pause did not work a single time!

In reply to Re^6: To organize pipe right way. by nikolay
in thread To organize pipe right way. by nikolay

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.