Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
From: Christopher Faylor <cgf@cygnus.com>
Message-ID: <19990208094644.A24171@cygnus.com>
Date: Mon, 8 Feb 1999 09:46:44 -0500
To: jmm@raleigh.ibm.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: pid problem found
References: <19990208093853.A24123@cygnus.com> <199902081443.JAA25182@jmm.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <199902081443.JAA25182@jmm.raleigh.ibm.com>; from jmm@raleigh.ibm.com on Mon, Feb 08, 1999 at 09:43:23AM -0500

On Mon, Feb 08, 1999 at 09:43:23AM -0500, jmm@raleigh.ibm.com wrote:
>> Umm.  Cygwin supports anonymous pipes.  Think UNIX.  That's what we're
>> trying to emulate.
>
>True enough... I should have said "Anon pipes created with CreatePipe
>and DuplicateHandle and inherited through CreateProcess"... unless
>I can swap out CreateProcess and the other stuff works (not saying
>that's not the case, just can't find an API call that claims to do
>this), then it's code re-write either way, and I might as well move
>the signal handling stuff over to events since that's pretty small
>code already (like I said, print an int and exit :)

Cygwin pipes are created with CreatePipe.  These pipes can be duplicated
with dup() or dup2().  They follow UNIX inheritance rules, i.e., they're
inherited by subprocesses by default.

That means that pipes will be inherited by processes that are
fork/execed or spawned.

Somehow I still get the feeling that you're making this a lot more
complicated than is warranted.

cgf

--   
Want to unsubscribe from this list?                             
Send a message to cygwin-unsubscribe@sourceware.cygnus.com