[dev] Issue with Config and opcode cache

[Remi Collet]

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

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.


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

iEYEARECAAYFAlQKvqoACgkQYUppBSnxahgvigCg9O2Qu4+xrkiyDcWMR3IzKMQb
fXgAnA2voMMfEXvwre0AMEIU5ywBMBqc
=NqUW
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: horde-opcache.patch
Type: text/x-patch
Size: 851 bytes
Desc: not available
URL: <http://lists.horde.org/archives/dev/attachments/20140906/044952c9/attachment.bin>