On 05/26/2010 08:59 AM, Eric Blake wrote:
> Several systems now offer execvpe(); it wouldn't be that hard to add a
> gnulib wrapper function that guarantees it everywhere.
>
>>
>> It doesn't hugely matter which semantics we have - which do you
>> suggest.
>
> I haven't exhaustively tested, but en
On 05/26/2010 08:44 AM, Daniel P. Berrange wrote:
>> The $PATH of the parent process, or the $PATH of the environment passed
>> to the child process? That can make a subtle difference, if one uses
>> virCommandAddEnvString(cmd, "PATH=...").
>
> I was going to say 'the same rules as execvp' but I
On Tue, May 25, 2010 at 11:56:15AM -0600, Eric Blake wrote:
> On 05/25/2010 07:24 AM, Daniel P. Berrange wrote:
> > We have had great success with our APIs for memory allocation and
> > string buffer management, removing most of the potential for incorrect
> > API usage, thus avoiding many common e
On 05/25/2010 07:24 AM, Daniel P. Berrange wrote:
> We have had great success with our APIs for memory allocation and
> string buffer management, removing most of the potential for incorrect
> API usage, thus avoiding many common errors. It is time todo the same
> for command execution.
Yes, this
We have had great success with our APIs for memory allocation and
string buffer management, removing most of the potential for incorrect
API usage, thus avoiding many common errors. It is time todo the same
for command execution.
This patch series is a proof of concept for a set of APIs I've
been
