Thank you @BlackbitDevs.

That'd be incorrect, open_basedir is not meant to replace PATH

That'd be incorrect, open_basedir is not meant to replace PATH

That was not my point. open_basedir and PATH are two completely different things. My point is that an executable that is available in the system does not necessarily have to be defined in PATH - but its location might be still hinted via the open_basedir setting in some environments.

However, since the usage of open_basedir is discouraged anyway, this likely will not matter that much in the end.

@fritzmg open_basedir is not about hinting about the location of executables at all.

@fritzmg open_basedir is not about hinting about the location of executables at all.

Not directly, no. But if a hosting environment employs open_basedir, it needs to add all paths to exectuables that the PHP environment should have access to to the open_basedir paths. Hence why open_basedir can be used as an additional source to finding executables via the ExecutableFinder.