Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64176
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEZPtU6fQCx+JdehkBL=DowTRn+qC4RqzkHPgX6-uZUuQPQOuA@mail.gmail.com>
References: <CAEZPtU6fQCx+JdehkBL=DowTRn+qC4RqzkHPgX6-uZUuQPQOuA@mail.gmail.com>
Date: Thu, 6 Dec 2012 10:52:13 +0100
Message-ID: <CAEZPtU4jG853qd4ip47fjVSEv2vt2mJqjhmnAOES7JF_ka+WpA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: Passing process handles to proc_open and co
From: pierre.php@gmail.com (Pierre Joye)

I mean bug #44942. Sorry.

Also to clarify for non C devs. A handle could be an opened file, a
pipe or similar resources. Also important to keep in mind that users
have to pass their own streams to proc_open if they like to pass or
receive data.

On Thu, Dec 6, 2012 at 9:49 AM, Pierre Joye <pierre.php@gmail.com> wrote:
> hi!
>
> While looking at the bug #63073, I was wondering if we could simply do
> not pass open handles to the newly created child process.
>
> The main issue in this bug is the session related handles. They are
> passed to the parent process, which hangs until their are closed. It
> indeed  does not happen (usually) until the end of the request. It
> makes these functions almost unusable as soon as sessions are used.
>
> These functions are about calling external commands and I fail to see
> which usage may require to access PHP related handles. Does anyone see
> any issue by not passing them anymore? And fixing this bug (and a
> couple of other I think)?
>
> It is windows only. Not sure if we do the same on other platforms.
>
> Cheers,
> --
> Pierre
>
> @pierrejoye



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org