perlprint has asked for the wisdom of the Perl Monks concerning the following question:

This node falls below the community's minimum standard of quality and will not be displayed.

Replies are listed 'Best First'.
Re: help me...named pipe
by marto (Cardinal) on Aug 21, 2009 at 08:55 UTC
Re: help me...named pipe
by jethro (Monsignor) on Aug 21, 2009 at 09:38 UTC
    You either need two threads or two scripts running as reader and writer of your pipe. Otherwise a pipe makes no sense.

    A pipe is a communication device, like the postal service or the telephone. Without at least two independent entities (people, processes, threads) there is no reason to communicate.

Re: help me...named pipe
by Marshall (Canon) on Aug 21, 2009 at 12:26 UTC
    Perl inter-process communication is easier than in some other languages because you can just use "print $filehandle" and the <$filehandle> syntax to read from the pipe once you have it open.

    There are of course pitfalls and gottcha's! Simplify the problem to a short set of code and post it along with errors encountered.

Re: help me...named pipe
by Jenda (Abbot) on Aug 24, 2009 at 16:49 UTC

    "b4"? Is that some tool? Some executable you're using? Or a protocol? Or ... oh wait, it's just an idiotic way to spell "before" ... OK.

    Step 1.: learn to spell
    Step 2.: learn to use the shift key. Sentences should start with a capital letter. It makes the text easier to read. And you DO want to make it easier to read. As easy to read and understand as you can. So that someone's wiling to waste (I mean, spend) their spare time to read it and help you. For free.
    Step 3.: do read some docs. How's "connect()" related to named pipes? What makes you think it is in any way related???

    Jenda
    Enoch was right!
    Enjoy the last years of Rome.

    A reply falls below the community's threshold of quality. You may see it by logging in.