X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: [Bug] Named Pipes (FIFO) / Bash Date: Mon, 24 Jan 2011 18:37:41 +0100 Lines: 24 Message-ID: <874o8yb3tm.fsf@Rainer.invalid> References: <87ipxgirl7 DOT fsf AT Rainer DOT invalid> <4D3D9E88 DOT 1050207 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Eric Blake writes: > Not just in bash, but in cygwin in general. Named pipes are still an > incomplete implementation, and until patches are written to get it > working more like posix, you can't expect them to work reliably. I said I knew that it wasn't working like POSIX pipes. Now, there's clearly a regression from 1.6->1.7. Before they just weren't working like POSIX pipes, but now they seem to be completely unuseable for synchronisation purposes. > Sorry, I don't have any. Autoconf is another client that would love to > use named pipes (for parallel testsuites), but which can't do so until > cygwin's implementation is completed. So, are you saying there's a development plan to get there, or not? :-) Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- 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