Monks-
I apparently don't understand what is going on with pipes here in Unix, please help.
The intent is to create 2 child processes from a perl script. The script writes to one child process, who passes that (via named pipe) to the second child process, who sends the data to stdout. The script then reads the data from child 2 and prints it.
use strict;
use warnings;
use FileHandle;
# Create named pipe...
my $pipe = "/tmp/mypipe";
system("ksh -c 'if [ ! -p $pipe ]; then mkfifo $pipe; fi'");
# Setup input process...
open(IN, '|-', "cat - > $pipe") || die "Can't open IN process: $!";
IN->autoflush(1);
# Setup output process...
open(OUT, '-|', "tail -f $pipe") || die "Can't open OUT process: $!";
OUT->autoflush(1);
# Send input...
my $input = '12345678901234567890123456789012345678901234567890';
print STDERR "Sending input...\n";
print IN $input;
# Read output...
print "Reading...\n";
my $line;
while($line = <OUT>) {
print $line
}
I've verified the pieces of this code work, but when I put it all together, I get nothing. What am I doing wrong?
Thanks
-Craig
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|