I am having a permission problem with the files being generated into the cache. It sounds similar to other issues I found in searching through the forum, but not identical. The cache directory and permissions there are setup properly I believe.
However, the host has it setup all screwy so that PHP is running as one user/group (apache?), but the files it creates end up as nobody. So if PHP/Etomite writes out a 644 permission file, then Etomite can't delete it later. Everything seems to be working fine, except that it chokes when it goes to delete the cached file.
What I think would work would be if the cache files where written out with 666 permissions. Is this something I can change?
I am using 0.6.1-RC2.
Thanks all!
Cache file permissions / Nobody user
Started by
DropDeadFred
, Mar 19 2008 04:34 PM
2 replies to this topic
#1
Posted 19 March 2008 - 04:34 PM
#2
Posted 19 March 2008 - 05:33 PM
Upgrade... We are no longer supporting that release of Etomite... A new release will be out "soon" but if you need to be up and running then I'd go ahead and upgrade to 0.6.1.4 ASAP... You are more than a few releases behind and the problem may be fixed already...
#3
Posted 19 March 2008 - 05:42 PM
Hmm, the problem you are having is a common one across the hosting world.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users










