Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-Authentication-Warning: ares.its.yale.edu: lsb32 owned process doing -bs Date: Mon, 2 May 2005 02:36:12 -0400 (EDT) From: Lev S Bishop To: cygwin AT cygwin DOT com Subject: Re: cygwin-1.5.16-1: FIFOs broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-YaleITSMailFilter: Version 1.2b (attachment(s) not renamed) 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>fff $ echo hello >&6 $ echo more >&6 .... $ exec 6>&- (or something similar). Or a more similar approach to your one also seems to work: $ cat <> fifo One thing that is different on cygwin to linux, is if there are multiple readers of a fifo. shell 1: $ cat fifo shell 2: $ cat fifo 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. Lev -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/