consider code that does something like the following:
apr_procattr_io_set()
/* we now have 6 pipe handles with no cleanup-for-exec on any */
apr_proc_create()
/* parent now has 3 of the pipe handles with no cleanup-for-exec on any */
apr_pool_cleanup_register(parent handle to child's stdin,
At 08:02 PM 5/23/2003, Jeff Trawick wrote:
consider code that does something like the following:
apr_procattr_io_set()
/* we now have 6 pipe handles with no cleanup-for-exec on any */
apr_proc_create()
/* parent now has 3 of the pipe handles with no cleanup-for-exec on any */
William A. Rowe, Jr. wrote:
At 08:02 PM 5/23/2003, Jeff Trawick wrote:
OWWW! That's a case I hadn't considered. However, the right answer
is to close the children's side of the pipes, always.
apr_proc_create() does that unconditionally in the parent path after fork()
it should be changed to
I don't remember discussion of this on [EMAIL PROTECTED] Work/life/family
have been insane, so I could have missed it.
One of the 'good things' (tm) of APR is that we should be providing
identical behavior across platforms, without the programmer having
to go through platform choices. Now, some
William A. Rowe, Jr. wrote:
I don't remember discussion of this on [EMAIL PROTECTED] Work/life/family
have been insane, so I could have missed it.
There wasn't one, at least not recently. I simply followed the design
that was there, adding another flag.
One of the 'good things' (tm) of APR is
