On Mar 17, 1:59 pm, Jeff Schwab <[EMAIL PROTECTED]> wrote:
>
> A Unix fifo is only nominally a file. It's really just a convenient way
> of referring to an in-memory object.
> mkfifo f
> some_prog > f &
> cat f
>
> Is semantically equivalent to:
>
> some_prog | cat
>
> If you w
waltbrad wrote:
> I'm proceeding slowly though the Lutz book "Programming Python". I'm
> in the section on named pipes. The script he uses has two functions:
> one for the child the other for the parent. You start the parent then
> the child:
>
> python pipefifo.py #starts the parent
>
> file /
On Mar 17, 1:50 pm, waltbrad <[EMAIL PROTECTED]> wrote:
>
> I then wanted to start the child process first and see what happened
> when I ran the parent. Well that works but the reads come out in
> random order.
Well, I take that back. I accidentally had two 'parent' processes
open. So, the reads
