[PHP-DEV] OPCache documentation
Hi all, As you know, 5.5 final is coming soon. We are in RC, so mainly stabilizing stuff and preparing the final release for anyone to setup 5.5 on their servers. I see the documentation migration guide has already been commited, that's a good new. I also see that new features we ship in 5.5 are online in the documentation, great ! But a crucial feature is missing doc : OPCache. As this feature is a very big step in PHP's life (we finally have a recommanded, bundled opcode cache system, and I'm very proud of this personnaly), I think it is crucial to have a good documentation about it. Has anyone started to write some doc about OPCache ? Another subject is APC. We have its doc on php.net, all right. What I would like is we patch APC doc when 5.5 final gets released, to clearly show our mind about it. That way, any people using 5.5 should be able to read in the doc that APC has support has been interrupted, that APC should never be used together with OPCache, and that OPCache is now the standard recommanded OPCode caching solution for 5.5, 5.4 and 5.3. It is crucial to communicate one this point for our users. Then will come the "User cache" debate Thank you. Julien.Pauli
[PHP-DEV] [PROPOSAL] apparmor change_hat functionality in fpm
Hi! The basic idea behind this is to get a better seperation of different php pools (so e.g. php scripts from one pool can't access the other and vice versa). I did a small patch (https://github.com/php/php-src/pull/343) that adds a configuration parameter to pools (apparmor_hat). If this is set, workers of the pool try to change the apparmor hat to the specified value. The patch only touches fpm. Only thing that's needed is libapparmor - if it is not there the functionality just gets left out. To keep things simple this version is very coarse - meaning it is not possible to change the hat back, or change to a different hat according to the executed script. Any thoughts on this? Cheers, Gernot
[PHP-DEV] [PROPOSAL] apparmor change_hat functionality in fpm
Hi! The basic idea behind this is to get a better seperation of different php pools (so e.g. php scripts from one pool can't access the other and vice versa). I did a small patch (https://github.com/php/php-src/pull/343) that adds a configuration parameter to pools (apparmor_hat). If this is set, workers of the pool try to change the apparmor hat to the specified value. The patch only touches fpm. Only thing that's needed is libapparmor - if it is not there the functionality just gets left out. To keep things simple this version is very coarse - meaning it is not possible to change the hat back, or change to a different hat according to the executed script. Any thoughts on this?
