Re: [Bug] Named Pipes (FIFO) / Bash

[Achim Gratz <Stromeko at nexgo dot de>]

Achim Gratz <Stromeko@nexgo.de> writes:
> In other words, opening the pipe is non-blocking, even though no
> listener is present.  Listing /proc/self/fd lists fd 6 as opened to FIFO
> /tmp/pipe, but any output to it blocks indefinitely.  I believe that the
> FIFO has in fact never been opened as far as the system is concerned.
> The output then blocks on the apparently not-open FIFO (I should be
> getting a SIGPIPE instead when trying to write into a pipe that has no
> listener).

I've checked again with the latest snapshot (2011-08-03), after doing a
full update and rebaseall.  While the FIFO implementation still does not
conform to POSIX w.r.t. blocking, it now gives consistent results again
(as it was in Cygwin 1.5), does not block listeners indefinitely anymore
and kills a listener with SIGPIPE when the producer goes away.  So if
the scripts are written to assume that behaviour, you can again use FIFO
to synchronize processes.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple