|
Because PHP is embedded within HTML, PHP web scripts cannot use a
shebang, so it is a necessity that the php-cgi binary
(/usr/bin/php-cgi in our environment) be executed with the script as
an argument, rather than the script being executed directly (or at
least this is my understanding, and I have not found any information
on the internet to the contrary). This creates a problem with the
requirement that all files executed by suexec be in the userdir,
because obviously the php-cgi binary is not. This situation is
unique to PHP, I think, because of the embedding in to HTML. That
said, PHP is incredibly common and I can't believe that a good
solution hasn't been created for this. At this point I'm thinking
the best solution is suphp and suexec alongside each other, because
suexec seems to have been poorly designed for handling scripts that
must be explicitly run with an interpreter (which, in its defence,
is only PHP that I'm aware of). Please let me know if I'm wrong on any of these points. On 10/26/2011 12:22 AM, Steve Swift wrote: I don't understand how suexec is "calling" php-cgi, and how such php scripts work. -- Jesse B. Crawford (jeanluc) Systems Programmer Tech Computer Center New Mexico Inst. of Mining & Tech. jeanluc@xxxxxxx // http://nmt.edu/~jeanluc |
|