$| = 1; select(PIPE);
is wrong. It sets autoflush for the previously select handle, not PIPE. It should be
my $old_sel = select(PIPE); $|=1; select($old_sel);
or the more readable
use IO::Handle qw( ); PIPE->autoflush(1);

Now that won't fix your problem. Since you proceed to close the pipe after every print, everything is being flushed even though you fail to turn on autoflush. However, once you fix autoflush, you won't have any reason to keep reopening and closing the pipe.

Now, I'm quite curious as to what you use <PIPE> to read from the pipe (with $/ left to its default) when the data sent over the pipe doesn't contains any newlines.

In reply to Re: IPC via named pipes, losing some messages by ikegami
in thread IPC via named pipes, losing some messages by ftumsh

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.