Re: Issue with Config and opcode cache

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 06/09/2014 09:58, Remi Collet a écrit :
> Hi,
> 
> When using an opcode cache, configuration files are cached.
> 
> So, after a configuration file is updated, its old content will be 
> served by cached until invalidated, or checked.
> 
> With Zend Opcache, default check delay is 2"
> 
> opcache.revalidate_freq=2
> 
> And, it is common to have a greater value on production env.
> 
> The small patch attached should fix this (only for opcache, other 
> opcode caches such as XCache or deprecated APC are not handled)
> 
> 
> Notice, this is just a quick fix, perhaps you could integrate the 
> feature in a different way, just want to raise the issue and a 
> possible fix.
> 

https://github.com/horde/horde/pull/102


> 
> Regards, Remi.
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlQXySgACgkQYUppBSnxahgYrQCgyHndmkoTvJPWuuZl0Td2ZUJd
T1wAnRpAgrjXFpdOW8Cq2GTSWE4Q5B7T
=A0G4
-----END PGP SIGNATURE-----
-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]