donncha: I’m actually one of DreamHost’s WordPress nerds. This issue only appears to be happening on our Private Server (VPS) offerings. Those users actually have their own /tmp space to write to on their Private Server, so distobj’s idea might not be a bad one.
Of course, I’m not the one who maintains this plugin… 😉 If you foresee any problems that could come up from this workaround, please let me know and I’ll gladly refrain from suggesting it to our customers.
boogah – Is there any way I can detect that the plugin is running on a DreamHost server? The plugin could either suggest using the /tmp folder or change the cache_dir to point there automatically if that what possible.
It seems to me to be a bad idea to cache the pages on a non-local drive in general, yesno? Perhaps some more generic approach to determine where the cache directory actually is might work?
It’s a very bad idea. NFS makes it hard to do file locking too. I don’t think there’s any way of automatically testing a directory but a FAQ for DreamHost (and others who use NFS) users would probably go a long way.
I’ll update the plugin this week with that.
donncha: A FAQ would be superb! If you happen to need any help getting it going, please let me know and I’ll gladly pitch in where needed. It’s partially our problem, after all.
As an addendum, one of our admins suggested the users name their caching directory in /tmp something unique. Since some users on shared hosting might name the directory whatever is suggested, this could cause problems and conflicts – and I’m sure we want to play it on the safe side, right?
boogah – if the tmp space is unique to each account then there won’t be any need for a random directory is there? If the tmp space is shared though then there’s a security risk writing cache files there.
donncha: Gah! Quite true. Must’ve had a bit of a brain fart there.
Since this only seems to happen on our Private Server offerings, the need for a unique directory shouldn’t be needed. Shared users don’t seem to run into this problem tho (which is odd as most of them also use NFS mounted storage) so suggesting they use /tmp really doesn’t need to happen.
What’s the maximum size of files you can put on /tmp ?
I have a lot more than 10M
I’m on a shared server, and I have CPU issues…
It would be very nice to have a cache directory to put our things to. It’s not so HD consuming.
What’s the maximum size of files you can put on /tmp ?
thats different from server to server.
How can I check what’s my amount?
I’ve about 200MB of cache files…
I’ve just signed up for DreamHost PS and want to use WP-Super Cache, but I’m afraid of having the same issues as described here. I see the fix described as changing the cache folder to ‘/tmp’, but when I look in my root folder, I don’t see a tmp folder, I just see a ‘domain.com’ folder, a ‘maildir’ folder, and a ‘logs’ folder. Could someone explain how I see the ‘tmp’ folder?
/tmp is not in your folder. You won’t see it.
Thanks Otto42,
Alright, so I’m on DreamHost P.S., I’ve got Super Cache set up, but I don’t know if it’s really serving up cached pages. Even after clearing my browser’s cache, the source doesn’t say it’s a cached page. I’ve got the latest version installed (0.8.1), I’ve changed the cache path in wp-cache-config.php to $cache_path = ‘/tmp/tpstart-wp-cache/’;
Can someone check if they’re seeing cached pages? http://www.2pstart.com/
I’d appreciate it!
I checked http://www.2pstart.com/category/blog/. It’s not serving cached pages.
If you look in your cache folder, do you see any supercache files being created?
