Date: Wed, 11 Apr 2012 17:39:51 -0000 (GMT)
From: "Gregory M. Turner" <gmt@malth.us>
To: cygwin@cygwin.com
Subject: Re: Process Substitution / Named Pipes in cygwin 1.7.11-1
Message-ID: <1f0f0eab-5f3c-48f7-a79f-befb90397894@malth.us>
In-Reply-To: <20120403083455.GP8014@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

----- Original Message (Corinna) -----
> On Apr  3 10:32, Sven Severus wrote:
> > On Apr 2 17:33, Corinna Vinschen wrote
> > > > Hello all,
> > > > 
> > > > I am running Cygwin DLL 1.7.11-1 and the bash command
> > > > "cat < <(echo 1234)" (not very profound, ok) works fine
> > > > on my Win7-64 box.
> > > > 
[snip]
> > >Does /dev/fd exist and is it a symlink to /proc/self/fd?
> > 
> > It does not exist.
> > 
[snip]
>  Why not start with
> 
>   ln -s /proc/self/fd /dev/fd

Reeeeeely!  I assumed it was just me, as I have an old-ish
self-compiled bash in a highly nonstandard environment.

I have the symlink, but my process-substitution-happy shell scripts
started breaking this way, recently, as well.

Mine die, suggestively, at /dev/fd/63.  They don't /always/ all die; but
somehow, I crossed some kind of rubicon and now they do all die.  If
I carefully smell the air afterwards there is the faint odor of scarce
OS resources leaking.  (Just kidding about that last part :P)

Haven't been able to clear out the process table or generally to
"get all diagnostic" on it yet; it's on my list but I really
must finish some paperwork for a certain government agency.

I'll get back to the list with whatever I can figure out about
this sometime soon.

-gmt

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