[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: posix_spawnp() and PATH - change code or manual ?
On Wed, May 06, 2020 at 02:29:07PM +0200, Joerg Sonnenberger wrote:
> On Wed, May 06, 2020 at 10:43:05AM +0200, Martin Husemann wrote:
> > On Wed, May 06, 2020 at 02:33:41PM +0700, Robert Elz wrote:
> > > Either of those is fine with POSIX - but we should really have one consistent
> > > policy. Changing either the manual or the code to match the other is also
> > > easy. What is not so easy is to decide which of the two (or perhaps
> > > something else, like perhaps using the results from a lookup of
> > > sysctl(user.cs_path)) we should actually do.
> > >
> > > Opinions?
> > Make the code follow the manual, it sounds usefull behaviour.
> I'm not sure. There is normally no way to force an empty environment
> variable, so if you want to not use PATH, the behavior of the current
> code is more useful.
Looking at execvp, it already has the (questionable) fallback to
_PATH_DEFPATH, so posix_spawnp should do the same.
Main Index |
Thread Index |