Christopher Faylor cygwin.com> writes:
>
> On Mon, May 02, 2005 at 02:36:12AM -0400, Lev S Bishop wrote:
> >On linux, both keep waiting for someone to write to the fifo. On
> >cygwin, when the second cat tries to listen on the fifo, they both
> >exit. I don't know how fifos are supposed to wor
On Mon, May 02, 2005 at 10:30:40AM -0400, Igor Pechtchanski wrote:
>On Sun, 1 May 2005, Christopher Faylor wrote:
>> If you want to more-or-less duplicate the behavior of 1.5.15 you can do
>> something like this:
>>
>> (echo 9&; echo YOUR TEXT HERE) > /tmp/FIFO
>
>This is pretty obvious from t
On Mon, May 02, 2005 at 02:36:12AM -0400, Lev S Bishop wrote:
>On linux, both keep waiting for someone to write to the fifo. On
>cygwin, when the second cat tries to listen on the fifo, they both
>exit. I don't know how fifos are supposed to work, but I'm guessing
>cygwin gets it wrong here.
Yes
On Sun, 1 May 2005, Jerry D. Hedden wrote:
> However, that said, the above WJFFM. In fact, it works more like
> linux in 1.5.16 than it does on 1.5.15, i.e., the cat command exits
> after printing "YOUR TEXT HERE" whereas it continues to block in
> 1.5.15.
>
> >> I tried the 4
On Sun, 1 May 2005, Christopher Faylor wrote:
> On Sat, Apr 30, 2005 at 09:52:28PM -0500, Ren? Berber wrote:
> >Jerry D. Hedden wrote:
> >[snip]
> >>> However, that said, the above WJFFM. In fact, it works more like linux
> >>> in 1.5.16 than it does on 1.5.15, i.e., the cat command exits after
>
cgf wrote:
> I thought that maybe something like:
>
> cat < FIFO 42>FIFO
>
> might work since that would cause cat to keep FIFO open for input and
> output but that just hangs on both cygwin and linux.
Probably the right thing to do is:
in one shell:
$ cat < fifo
in the other shell:
$ exec 6>f
However, that said, the above WJFFM. In fact, it works more like
linux in 1.5.16 than it does on 1.5.15, i.e., the cat command exits
after printing "YOUR TEXT HERE" whereas it continues to block in
1.5.15.
>> I tried the 4/30 snapshot of cygwin1.dll. It exhibited the behavior
On Sat, Apr 30, 2005 at 09:52:28PM -0500, Ren? Berber wrote:
>Jerry D. Hedden wrote:
>[snip]
>>> However, that said, the above WJFFM. In fact, it works more like linux
>>> in 1.5.16 than it does on 1.5.15, i.e., the cat command exits after
>>> printing "YOUR TEXT HERE" whereas it continues to bloc
Jerry D. Hedden wrote:
[snip]
>> However, that said, the above WJFFM. In fact, it works more like linux
>> in 1.5.16 than it does on 1.5.15, i.e., the cat command exits after
>> printing "YOUR TEXT HERE" whereas it continues to block in 1.5.15.
>
>
> I tried the 4/30 snapshot of cygwin1.dll. It
Christopher Faylor wrote:
On Sat, Apr 30, 2005 at 08:38:17PM -0400, Jerry D. Hedden wrote:
I have a client-server application written in Perl that reads and writes
using FIFOs. It works fine under cygwin-1.5.15-1, but fails under
cygwin-1.5.16-1 because it cannot read from the FIFO.
To test thi
On Sat, Apr 30, 2005 at 08:38:17PM -0400, Jerry D. Hedden wrote:
>I have a client-server application written in Perl that reads and writes
>using FIFOs. It works fine under cygwin-1.5.15-1, but fails under
>cygwin-1.5.16-1 because it cannot read from the FIFO.
>
>To test this, open two shells.
> I have a client-server application written in Perl that reads
> and writes using FIFOs. It works fine under cygwin-1.5.15-1,
> but fails under
> cygwin-1.5.16-1 because it cannot read from the FIFO.
>
> To test this, open two shells. In one shell, type:
> cd /tmp
> mkfifo FIFO
> cat
> In t
12 matches
Mail list logo
