Just a note, in most cases where you have your own private /tmp it is
not the same /tmp PHP uses. You are in a chrooted or jailed environment
with a virtual /tmp where usually Apache runs outside this restricted
environment , the biggest reason being running a seperate set of Apache
processes would be very expensive on the resources. If you are using
Ensim this is the way it is setup and a few other environments I know of
do the same thing.
In this case changing your virtual /tmp ownership would not help
Apache/PHP not being able to write to /tmp.
Jason
Curt Zirzow wrote:
The problem is already isolated. the /tmp directory needs to have
the correct permissions.
Curt
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
