This is quite odd: I mean, regardless of whether your or his/her Gregarius installation is writing to /tmp/magpierss, bit processes should be owned by apache, there shouldn't be any permission conflicts! Unless... (picture of light bulb over my head) ... unless you update via a cron job! The fact that several users share the same cache directory is actually desired, so as to avoid downloading a given feed twice. What we should be doing is append the uid of the process writing into the cache to the directory name. How does that sound? > Someone else on my shared hosting server took control of > /tmp/magpierss with his /her version of gregarius after the tmp > directory was wiped. So the magpie cache system stopped caching stuff > for me. If you are user styles on server gage.dreamhost.com I am gonna > get you... (just kidding) > > On a more serious note, I did change the value of my cache directory > and everything works fine now but maybe we should replace the > magpie-cache default with > /tmp/magpierss-[random 4 digits] to minimize the chance of collisions. > We could also warn users with a small warning if the cache directory > is not writeable by apache. >