Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Hosting Requirements /

What you need to consider when choosing a hosting provider and plan.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Problem: Cache using file locking with NFS


Go to End


3 Posts   661 Views

Avatar
shrike

Community Member, 17 Posts

14 September 2016 at 8:23pm

Hi,

Customer is hosting SilverStripe in shared environment and their support said that CMS is not working with their environment, because of file locking in cache which is not working with NFS. They changed the core like this:

framework/thirdparty/Zend/Cache/Backend/File.php:

protected $_options = array(
'cache_dir' => null,
'file_locking' => false,
'read_control' => true,
'read_control_type' => 'crc32',
'hashed_directory_level' => 0,
'hashed_directory_umask' => 0700,
'file_name_prefix' => 'zend_cache',
'cache_file_umask' => 0600,
'metadatas_array_max_size' => 100

How should we proceed with this? Is it possible to make this setting inside config (to make installation update-proof) or is it even wise to change this setting at the beginning?

Avatar
shrike

Community Member, 17 Posts

5 January 2017 at 10:33pm

Any help with this?

Avatar
swaiba

Forum Moderator, 1899 Posts

6 January 2017 at 5:47am

Hi shirke,

We have all kinda moved to use a Slack channel now (or at least I think we have lol) so I'd advise asking here... https://www.silverstripe.org/blog/community-slack-channel/

Your post makes me think of something wmk has blogged about here... http://www.silverstrip.es/blog/speed-up-a-vagrant-machine-on-windows/ (but that is just a guess it might relate).

Best bet is to ask on slack - and as I say look out for wmk or comment on the blog post to get his attention (I think he'd like a comment on the blog post :) )