Forum Moderators: phranque
Basically, I've been running Apache with an suexec that chroots users for a while. Each user has their own mini-environment, with their own php binary. This is great for security.. if there's a php bug or something, one site might get defaced, but it limits them from expanding to the system.
The problem is, with a decent amount of traffic, this is faaar too much overhead. I need to know how to run use fast-cgi.
Basically, as I see it, it would work like this, request is made to vhost, some wrapper opens a connection to the fast-cgi daemon, passes the scriptname, uid, gid. FastCGI then goes to their webspace and execs the script as them, chrooted to their dir. So it runs as it would if they had their own php binary, but everyone shares the same binary through the fastcgi daemon.
My question is, can I still chroot like this? Can I make fastCGI chroot the script to it's home dir? If not, that kind of negates having a chroot at all.
I'm open to all thoughts and suggestions!
Thanks!
Welcome to WebmasterWorld!
I can't answer your question, but maybe bumping it up on the active list will attract the attention of someone who can...
-Bump-
Jim
