Do you have experience with pipes in other languages, like Perl? In the pipes I have used in Perl, I have to spawn a child process for pipe communication, and that process has to obey the IO protocol: responding to defined commands. Also, I have to open two pipes, one for reading and one for writing.
rdr = pipe for reading wdr = pipe for writing &open2 spawns a new process and opens two pipes. #!/usr/bin/perl require "fopen2.pl"; print "I am starting to run...\n"; $NewPID=&open2(rdr, wdr, "kermit"); print "The new pid is: ", $NewPID, "\n"; print wdr "take world28\n"; #$NumRead = read( rdr, $buf,80 ); $ho = <rdr>; print $ho; $ho = <rdr>; print $ho; $ho = <rdr>; print $ho; $ho = <rdr>; print $ho; $ho = <rdr>; print $ho; #print $NumRead, "\n"; $NumRead = read( rdr, $buf,80 ); print <rdr>; print $NumRead,"\n"; $NumRead = read( rdr, $buf,1000 ); print $NumRead, "\n"; $NumRead = read( rdr, $buf,2000 ); print $NumRead,"\n"; kill 9, $NewPID; Of course, I have not had kermit on my system for (ahem) 6 years. mike_lachaine wrote: > Hello, > I spent a few hours trying to figure out what is wrong with the named > pipes vi's (LabVIEW 7 on redhat linux FC1). I open a pipe for > read/write (and doing a ps shows that the command line is running) I > write to it but I read nothing!. No errors from the vi's error > outputs, neither from the standard error (probably I can't read from > there either...). I close the read/write pipe, ps shows that command > is not running anymore. Nothing from the logs also. Everything seems > to be fine but I can't read!.
