phpsuexec - can it really effect a script having this feature on?

[chris8lunch]

Why would someone NOT use "phpsuexec"? From what I know, doesn't it just make users not be able to set/use permissions "777" for files? What if a script asks to use 777 but you do 755? Would it be a problem??

Some say it doesn't even help having it on.. Could some people please advise and post your feedback about it?

Thanks!!

 

[mohit]

phpsuexec is safer

hi,
phpsuexec is safer, cause it doesn't needs your folder to be WORLD WRITEABLE(chmod 777) anymore still your scripts can edit/create files from the same user a/c.

however certain scripts might need a little fix to be done manually.
eg: oscommerce.

see ya,
mohit

 

[Stefaans]

PhpSuexec affects only PHP scripts and the environment they are working in. As mohit mentioned, neither the PHP script itself and the directory it resides in may be world writable.

For Perl scripts, you will still need to set privileges to 755. Being a Perl (and not PHP) scripts, PhpSuexec does not come into the picture when executing the script.

 

[chris8lunch]

Well from what I have heard, what you guys have said and my experience, I suggest not even enabling it.. I use to get many tickets saying the client has problems with the script ect. ect. Now that I have turned it off, no more bogus tickets.. About 40% of them made up this issue caused by that!

If its world writable file, that is their problem, or is it not?

 

[Stefaans]

We have been using PhpSuexec on all our servers for a long time now. After enabling it initially, there were some issues. Now it is pretty much trouble free.

Note that after running easyapache and enabling PhpSuexec, another script (forgot its name) will run for 24 hours, constantly checking the Apache error_log for PHP permission problems, and fixing them on the fly. And fixing file permissions manually isn't so difficult either.

Staying away from PhpSuexec may be the easier route for you. However, if I was in your shoes, I would take the plunge and deal with problems as the occur. A rough day or two, and then you'll be in the clear

 

[chris8lunch]

We have been using PhpSuexec on all our servers for a long time now. After enabling it initially, there were some issues. Now it is pretty much trouble free.

Note that after running easyapache and enabling PhpSuexec, another script (forgot its name) will run for 24 hours, constantly checking the Apache error_log for PHP permission problems, and fixing them on the fly. And fixing file permissions manually isn't so difficult either.

Staying away from PhpSuexec may be the easier route for you. However, if I was in your shoes, I would take the plunge and deal with problems as the occur. A rough day or two, and then you'll be in the clear

Well I would have issues like "my script won't let me finish installing because it says my permissions arn't set to 777", or "my script isn't working correctly because permissions 755 isn't working for what it needs.." and alot of times clients would simply tell me that they couldn't get their script to work so they want a refund and leave. They don't even care to try and get the issue resolved.

I will never enable this stupid crap again.