Bug #68965 [Opn->Dup]: Opcache could not be used in conjunction with php-fpm chroot

From: Date: Thu, 30 Jun 2016 09:09:56 +0000
Subject: Bug #68965 [Opn->Dup]: Opcache could not be used in conjunction with php-fpm chroot
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-201929@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=68965&edit=1

 ID:                 68965
 Updated by:         requinix@php.net
 Reported by:        exception0x876 at gmail dot com
 Summary:            Opcache could not be used in conjunction with
                     php-fpm chroot
-Status:             Open
+Status:             Duplicate
 Type:               Bug
 Package:            opcache
 Operating System:   Gentoo Linux
 PHP Version:        5.5.21
 Block user comment: N
 Private report:     N

 New Comment:

(mentioning bug #67141 for the automatic backlink)


Previous Comments:
------------------------------------------------------------------------
[2016-06-30 09:08:08] requinix@php.net

Related To: Bug #72521

------------------------------------------------------------------------
[2015-11-10 01:31:02] spamto at mailinator dot com

Hi, we are experiencing the same problem, as well as a number of other users (see bug 67481 https://bugs.php.net/bug.php?id=67481). For now we
disable file opcache in chrooted environments (all of our environments) but that's a pity file
opcache provides a significant improvement in performance and server load.

------------------------------------------------------------------------
[2015-02-11 23:22:48] public+php dot net at bastelstu dot be

This appears to be a duplicate of: https://bugs.php.net/bug.php?id=67141

------------------------------------------------------------------------
[2015-01-31 19:59:05] exception0x876 at gmail dot com

Description:
------------
It caches files by its full path so if there are same file paths under different chroots (take
/config.php as an example), it serves incorrect cached file. One of the possible solutions I can
think of is to add some additional info for cached file (like filesize, md5sum, filesystem inode
etc.)

Expected result:
----------------
Correct file served from cache for dirrefent chroots.

Actual result:
--------------
Incorrect file served from cache.


------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=68965&edit=1

Thread (4 messages)

« previous php.bugs (#201929) next »