From dev-return-11971-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Fri Jun 11 16:28:12 2004 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 66838 invoked from network); 11 Jun 2004 16:28:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Jun 2004 16:28:11 -0000 Received: (qmail 21676 invoked by uid 500); 11 Jun 2004 16:28:19 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 21644 invoked by uid 500); 11 Jun 2004 16:28:18 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 21626 invoked by uid 99); 11 Jun 2004 16:28:18 -0000 Date: Fri, 11 Jun 2004 17:27:57 +0100 From: Joe Orton To: dev@apr.apache.org Subject: Re: apr_proc_create() cmdtype flavors and environment inheritance; incompatible API change desired? Message-ID: <20040611162757.GC26983@redhat.com> Mail-Followup-To: dev@apr.apache.org References: <40C9D2DB.9000707@attglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <40C9D2DB.9000707@attglobal.net> User-Agent: Mutt/1.4.1i X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Fri, Jun 11, 2004 at 11:42:19AM -0400, Jeff Trawick wrote: > whether or not the envionment is inherited should be orthogonal to some > other details of starting the program (via shell, searching or not > searching PATH), but API does not reflect that > > I need a way to start the new process via the shell *and* inherit the > environment of the calling process, but there is no such support at present. > > attached patch simplify_patch changes how the app tells APR whether or not > environment should be inherited in general, reducing the number of cmdtype > enums and at the same time increasing the number of ways apr_proc_create > can be used; this seems appropriate for 1.0 Sounds good in theory, but do all these combos have direct maps to an exec* though? I don't see an exec* which takes an env pointer and searches $PATH for the program, for instance... > attached patch extend_patch adds yet another cmdtype flavor so app can > specify to run the command via the shell and have it inherit the > environment of the calling process; this seems appropriate for 0.9 Actually, doesn't that happen by default already on Unix? It's passing the env pointer through to execve, right? joe