Bug #67481 [Com]: Opcache uses wrong file from cache

From: Date: Mon, 08 Aug 2016 11:05:54 +0000
Subject: Bug #67481 [Com]: Opcache uses wrong file from cache
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-203075@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=67481&edit=1 ID: 67481 Comment by: rgpublic at gmx dot net Reported by: Danack at basereality dot com Summary: Opcache uses wrong file from cache Status: Closed Type: Bug Package: opcache Operating System: Centos PHP Version: 5.5.13 Block user comment: N Private report: N New Comment: Related to/Duplicate?: https://bugs.php.net/bug.php?id=69090 Previous Comments: ------------------------------------------------------------------------ [2015-11-10 01:31:03] spamto at mailinator dot com Related To: Bug #68965 ------------------------------------------------------------------------ [2015-09-03 10:39:46] admin at 3dr dot org We can confirm that. Because of this bug opcache is unusable in chroot. ------------------------------------------------------------------------ [2015-06-06 06:03:56] kelemen dot samuel at gmail dot com op cache is really unusable with identical applications (same or similar directory structure) on same hosting. We need more specify cache for one file, eg. absolute filepath? Or if this is how opcache was designed then disable this feature by default. ------------------------------------------------------------------------ [2015-03-05 12:16:30] tomek at lutel dot pl @Danack at basereality dot com Why do you say its different issue? Chrooting is impossible with webcache due to faulty opcache file handling. Could you reopen this bug please, and not call it a feature please? :) ------------------------------------------------------------------------ [2015-01-05 14:39:11] Danack at basereality dot com @public+php dot net at bastelstu dot be + @spam at rw23 dot de Those are different cases from the issue that I originally reported. Please open a separate feature request. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=67481 -- Edit this bug report at https://bugs.php.net/bug.php?id=67481&edit=1

« previous php.bugs (#203075) next »