Solved Heads up! php exec() does not look in /usr/local/bin/ for executables

[nik0tine]

it only sees stuff in /usr/bin/

hope this helps guys peace

 

[ljboiler]

Perhaps the PATH environment variable doesn't have /usr/local/bin in it.

 

[nik0tine]

so in the terminal if i type-in:

which tesseract

it shows:

/usr/local/bin

but user www (apache) does not index those bin's
Can you please suggest a PATH export command to fix it ljboiler? Thank you!!

 

[SirDice]

Don't rely on PATH. Use fully qualified paths, especially in scripts.

 

[ljboiler]

I agree with SirDice. You don't want to open up apache+php to exec-ing things based on searching a PATH - use the full path in the exec call.

 

[nik0tine]

Don't rely on PATH. Use fully qualified paths, especially in scripts.

Hi Dice! yes indeed, I used the full path to the bin. (it was tesseract) in a protected (private) php function.
This got me investigating since i copied a php script from an ubuntu server to the freebsd12 system and ran it (no dependency issues, identical setups) but on the ubuntu it exec()'s as expected, on freebsd it wants the full path. No problem, in fact, I prefer the way the BSD behaves.

 

[SirDice]

This got me investigating since i copied a php script from an ubuntu server to the freebsd12 system and ran it (no dependency issues, identical setups) but on the ubuntu it exec()'s as expected,

Probably because on a lot of Linux distributions everything but the kitchen sink gets dumped in /usr/bin. Still shouldn't rely on that. What if someone placed a (backdoored) executable just a little higher up the PATH chain? That's the main reason why you should not rely on PATH in scripts.

 

[nik0tine]

You all are gems! Thank you kindly and happy holidays guys!