a simple "$fifodata = <FIFO>;" has always worked here (though I'll admit sysread() is probably better).

Is is better simply because using buffered IO with select is wrong.

The only reason I even tried using sysread() instead was in case <FIFO> was somehow leaving something on the FIFO

Leaving stuff on the FIFO is fine. <FIFO> is bad because it can return less than what it reads from the FIFO. That causes select to block when it shouldn't. For example, 

use IO::Select qw( );
use IO::Handle qw( );

pipe(my $rfh, my $wfh) or die;
$wfh->autoflush(1);

if (fork()) {
    my $sel = IO::Select->new($rfh);
    while ($sel->can_read()) {
        my $got = <$rfh>;
        last if !defined($got);
        chomp $got;
        print("It took ", (time()-$got), " seconds to get the msg\n");
    }
} else {
    for (;;) {
        print($wfh time(), "\n") or die;
        print($wfh time(), "\n") or die;
        sleep(3);
    }
}

[download]
It took 0 seconds to get the msg
It took 3 seconds to get the msg
It took 0 seconds to get the msg
It took 3 seconds to get the msg
It took 0 seconds to get the msg
...

[download]

But with sysread: 

    my $sel = IO::Select->new($rfh);
    my $buf = '';
    while ($sel->can_read()) {
        sysread($rfh, $buf, 64*1024, length($buf)) or last;
        while ($buf =~ s/^(.*)\n//) {
            my $got = $1;
            print("It took ", (time()-$got), " seconds to get the msg\
+n");
        }
    }

[download]
It took 0 seconds to get the msg
It took 0 seconds to get the msg
It took 0 seconds to get the msg
It took 0 seconds to get the msg
It took 0 seconds to get the msg
It took 0 seconds to get the msg
...

[download]

I point out again that this select() call used to work, and has not been changed since then;

And select is still working properly. The problem has nothing to do with select.

because every select() call on the FIFO after the first command is read from it is saying that there is data on the FIFO to read

No, it's saying that the handle needs to be serviced. Specifically, it needs to be closed because it reached EOF. I explained this. Stop using select on a handle you're told is closed.

In reply to Re^3: Malfunctioning select() call on a FIFO by ikegami
in thread Malfunctioning select() call on a FIFO by Llew_Llaw_Gyffes

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.