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
X-Authentication-Warning:	ares.its.yale.edu: lsb32 owned process doing -bs
Date:	Thu, 14 Apr 2005 09:22:42 -0400 (EDT)
From:	Lev S Bishop <lev DOT bishop AT yale DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	Re: Bash Process Substitution
Message-ID:	<Pine.LNX.4.44.0504140911460.26500-100000@ares.its.yale.edu>
MIME-Version:	1.0
X-YaleITSMailFilter:	Version 1.2b (attachment(s) not renamed)

Corina wrote:
> In the Linux kernel there's some magic
> going on which we can't reproduce in Cygwin so far.  Trying to open
> an existing pipe for writing or reading opens apparently exactly the
> right end of the pipe under Linux.  On Windows, you only get the exact
> end of the pipe which is already available to the current process.  That's
> the read side of the pipe, AFAICS, and that doesn't allow writing.  This
> explains the "Permission denied".

Interesting. Looking in function process_substitute in subst.c, I can see 
that bash tries to swap ends of the pipe depending on whether its a >(cmd) 
or a <(cmd) substitution. 

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/

- Raw text -