Re: Problem with named pipes

2018-12-11 Thread Corinna Vinschen
On Dec 11 14:42, Ken Brown wrote: > On 1/8/2016 3:50 PM, Corinna Vinschen wrote: > > On Dec 25 16:39, Ken Brown wrote: > >> I've noticed a difference between Cygwin and Linux involving named pipes. > >> I > >> don't know if this a bug or simply a difference. > >> > >> Consider the following two s

Re: Problem with named pipes

2018-12-11 Thread Dan Kegel
On Tue, Dec 11, 2018 at 6:42 AM Ken Brown wrote: > > Very tricky problem. The FIFO code falls over its own feet trying to > > handle more than one writer (exec 7> is the first, echo blah is the > > second writer). Sigh. This code needs a thorough rewrite... > > I'm coming back to this thread af

Re: Problem with named pipes

2018-12-11 Thread Ken Brown
On 1/8/2016 3:50 PM, Corinna Vinschen wrote: > On Dec 25 16:39, Ken Brown wrote: >> I've noticed a difference between Cygwin and Linux involving named pipes. I >> don't know if this a bug or simply a difference. >> >> Consider the following two scripts: >> >> $ cat fifo1.sh >> #!/bin/sh >> set -x

Re: Problem with named pipes

2016-01-08 Thread Corinna Vinschen
On Dec 25 16:39, Ken Brown wrote: > I've noticed a difference between Cygwin and Linux involving named pipes. I > don't know if this a bug or simply a difference. > > Consider the following two scripts: > > $ cat fifo1.sh > #!/bin/sh > set -x > rm -f foo > mkfifo foo > exec 7>foo > echo blah > f

Problem with named pipes

2015-12-25 Thread Ken Brown
I've noticed a difference between Cygwin and Linux involving named pipes. I don't know if this a bug or simply a difference. Consider the following two scripts: $ cat fifo1.sh #!/bin/sh set -x rm -f foo mkfifo foo exec 7>foo echo blah > foo $ cat fifo2.sh #!/bin/sh set -x read bar < foo echo

RE: 1.5.19: Problem with Named Pipes

2006-03-30 Thread Dave Korn
On 30 March 2006 05:31, Nate wrote: > To illustrate the problem make two named pipes: > > mknod -m 0600 pipe1 p > mknod -m 0600 pipe2 p > So, now open three shells. In these shells, execute the commands in every > possible order, and you will see that the following order does not work: > > ls

1.5.19: Problem with Named Pipes

2006-03-29 Thread Nate
I am running Cygwin 1.5.19, and I'm experiencing some problems with named pipes. When reading from and writing to a named pipe, it should not matter which process starts first, but I have found a condition which Cygwin does not handle. To illustrate the problem make two named pipes: mknod -m 06