where.php: PATH needs to be set

[tariqbuilds]

where.php: PATH needs to be set

[tariqbuilds]

does it work when the command within the where.php file is changed from which to whereis?

We recently made some changes to that file and if those changes are the culprit, we can always revert.

If not, we can try to put a conditional clause to detect nginx + php-fpm to try to resolve this solution too.

[commonquail]

In general, having to hard-code PATH does not seem ideal. Is it not being picked up or is which not in PATH by default?

[pschmitt]

@commonquail Whether which is in the PATH or not isn't relevant, since which gets called directly (/usr/bin/which).

@afaqurk The whereis.php from 96496f6 works just fine.

[tariqbuilds]

This means that we can either:

1. Revert back to whereis rather than which
2. Write conditional code in where.php to detect nginx/apache and execute appropriate command

tough choice. What do you guys think?

[commonquail]

@pschmitt: I meant php, not which. Sorry.
I'm still unclear on why whereis works but which doesn't.

[pschmitt]

whereis searches the standard *nix locations for a specified command.

which searches your user-specific PATH (which may include some of the locations whereis searches, and may not include others - it might also include some places that whereis doesn't search if you'd added to your PATH)

http://superuser.com/a/40302

Note that there also the where, type, command and hash shell buildins that may be used to check whether a command is available or not, but that would require spawning a shell for each and every check.

From what I read, command would be the standard, POSIX way, of doing this.

[commonquail]

POSIX 2004 command specification, Bash and KornShell support confirmed. That seems reasonable.