Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 2 May 2005 11:04:08 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin-1.5.16-1: FIFOs broken
Message-ID: <20050502150408.GC29132@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <427424F9 DOT 8060209 AT 1979 DOT usna DOT com> <20050501010945 DOT GB21071 AT trixie DOT casa DOT cgf DOT cx> <42743E33 DOT 1020700 AT 1979 DOT usna DOT com> <d51ftk$vj9$1 AT sea DOT gmane DOT org> <20050501052345 DOT GA25851 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT GSO DOT 4 DOT 61 DOT 0505021023430 DOT 5266 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.61.0505021023430.5266@slinky.cs.nyu.edu>
User-Agent: Mutt/1.5.8i

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 99999&; echo YOUR TEXT HERE) > /tmp/FIFO 
>
>This is pretty obvious from the context and the following paragraph, but
>just to clarify for the archives: the above should be
>
>(sleep 99999&; echo YOUR TEXT HERE) > /tmp/FIFO

Actually, it should be:

(sleep 99999& echo YOUR TEXT HERE) > /tmp/FIFO

i.e., no semicolon.

But, then, 'cat <>' is better.

cgf

--
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/