Doc #72521 [Opn->Dup]: Document PHP-FPM chroot() issues with the opcode cache

Edit report at https://bugs.php.net/bug.php?id=72521&edit=1 ID: 72521 Updated by: requinix@php.net Reported by: janos at pasztor dot at Summary: Document PHP-FPM chroot() issues with the opcode cache -Status: Open +Status: Duplicate Type: Documentation Problem Package: Documentation problem Operating System: Linux/Unix PHP Version: Irrelevant Block user comment: N Private report: N New Comment: The issue should be addressed, rather than simply having it documented. As noted elsewhere a simple "cache prefix" or similar would (probably?) be sufficient. Previously reported as bug #68965 and bug #67141. Previous Comments: ------------------------------------------------------------------------ [2016-06-30 09:02:05] janos at pasztor dot at Description: ------------ When using the chroot functionality with PHP-FPM and having the same path within the chroots of two different pools, the opcode cached code can get mixed up. For example these two scripts get mixed up with opcode cache name: Full path 1: /var/www/example1.com/var/www/htdocs/index.php Chroot 1: /var/www/example1.com Full path 2: /var/www/example2.com/var/www/htdocs/index.php Chroot 2: /var/www/example2.com Expected result: ---------------- Update the documentation at https://secure.php.net/manual/en/install.fpm.configuration.php with a warning, something like this: chroot string Chroot to this directory at the start. This value must be defined as an absolute path. When this value is not set, chroot is not used. >>> Be careful when using chroot with opcache! Since the opcache is shared between pools, >>> the paths within the chroots must be unique per chroot, otherwise the opcache will lead to >>> unexpected behavior. <<< (Alternatively the FPM pool name could be added to the opcache key to avoid this behavior.) ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=72521&edit=1