No, I think this is a real bug. You can't run something like /bin/ls through suexec as things stand now. Fixing it is another issue.
On Thu, 24 Apr 1997 [EMAIL PROTECTED] wrote: > Synopsis: suexec and server side includes > > State-Changed-From-To: open-feedback > State-Changed-By: [EMAIL PROTECTED] > State-Changed-When: Thu Apr 24 08:04:55 PDT 1997 > State-Changed-Why: > The suexec-bounded environment is very restricted, for > obvious reasons. One of the restrictions is a severely > limited PATH envariable. The PATH is set to > "/usr/local/bin:/usr/bin:/bin". However, I should think > that your ls(1) command should be found somewhere in > there. What does the error log contain regarding the > #exec cmd request? >
