This is probably a tricky one to answer, but I can't find any real info on Google.
I've run in to a minor limitation caused by suEXEC, in that it doesn't allow me to change the permission of my CGI-BIN to 775 or 777. This isn't critical to my project, but would definitely help simplify things; with suEXEC, I'll have copies of the same script in multiple accounts, and if I make a change then I have to go change each copy manually.
So, the questions are:
1. Do I even need suEXEC? Every account on the server belongs to me, so security isn't a big issue; if they're logged in as me, they have root access, anyway.
2. If it's really important, is there a way to get around suEXEC's requirement that the CGI-BIN not be writable by others?
I've run in to a minor limitation caused by suEXEC, in that it doesn't allow me to change the permission of my CGI-BIN to 775 or 777. This isn't critical to my project, but would definitely help simplify things; with suEXEC, I'll have copies of the same script in multiple accounts, and if I make a change then I have to go change each copy manually.
So, the questions are:
1. Do I even need suEXEC? Every account on the server belongs to me, so security isn't a big issue; if they're logged in as me, they have root access, anyway.
2. If it's really important, is there a way to get around suEXEC's requirement that the CGI-BIN not be writable by others?