That's the way it works since Apache runs as a single user id. There is no way PHP can escape this. You might look into setting this user up with the open_basedir restriction instead of safe_mode. Under open_basedir the user's scripts can only manipulate files under the directory you specify.
Your other options are running PHP in CGI mode under suExec (a bit slow and clunky) or running multiple instances of Apache behind a reverse proxy like Squid where you configure Squid via something like SquidGuard to send requests to various ports on localhost based on which domain is being requested. Then you would set up multiple instances of Apache each listening to a different port on localhost and each running as that user's user id. The last option is the most powerful, but is also somewhat more resource intensive. -Rasmus On Fri, 29 Mar 2002, Kai Schaetzl wrote: > One of our customers installed a CMS application scripted in PHP and > it creates a lot of new files. These are all getting created under > the userid of nobody (the webserver's id) instead of the user's id > (the scrip's id) which makes it somewhat difficult to run the > application in safemode because here and then it will run into a > barrier. Is this a problem with the coding or will PHP always create > new files under the webserver's user id? > > > Kai > > -- > > Kai Schätzl, Berlin, Germany > Get your web at Conactive Internet Services: http://www.conactive.com > IE-Center: http://ie5.de & http://msie.winware.org > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
