From: David E. M. <de...@et...> - 2005-01-19 09:18:35
|
> actually, given your clarification above, i would have guessed that the > problem is that wwwrun needs +rw access to the base dir and everything > inside of it. that is, your base dir might need to be owned by > webuser:wwwclient, but for file manager to work right, Apache needs wri= te > access to the base..... oh, wait. egads, you've opened the basedir up = to > the world! you sure you want to do that? maybe an option would be to = add > apache to the wwwclient group instead. You're right, letting the world write to the base dir is not the safest, but convenient for testing. > i would also think safe_mode_include_dir might work; keep looking. migh= t > be related to ownership/permissions of the included dirs, who knows.... After reading a "bug-report" (http://bugs.php.net/bug.php?id=3D20054) concerning the same matter I found out that the safe_mode_include_dir variable only lets you read files from that directory. This explains also why I get the same error when setting the base dir to the default value "/usr/local/lib/php" of safe_mode_include_dir in the php.ini file. Since I always get the warning that the script owned by webusr is not allowed to use opendir() on the base directory owned by wwwrun, I come to the conclusion that either: -) you need to turn off safe mode, or -) apache needs to run as user owning the script, which in turn would not work in a virtual hosting environment. But since this plugin is around for a while, I doubt that I am right... ;= -) |