Web lists-archives.com

Re: Use a default path in exec*p*() if PATH is unset?

On 4/12/2017 12:41 PM, Christian Franke wrote:
> cyg Simple wrote:
>> ...
>> But I don't believe that env --ignore-environment should be using execvp
>> and should be using execv instead.  That is for the upstream coreutils
>> team to decide though.
> Possibly not, as it would also require to check whether PATH is set
> later in the command line.
> Always using execv() if -i is specified would break:
>   env -i PATH=/bin:/usr/bin prog

Good!  --ignore-environment is just that regardless of where the
environment is set.

> To force execv()-like behavior with -i, simply use
>   env -i PATH=. prog

But this is what should occur anyway.

cyg Simple

Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple