On 2019-10-28 17:30, Eric Krona wrote: > This is a long-standing issue with the opcache, its frequently seen when > deploying code using a symlink swap as the final step to atomically launch > the new code.
Thank you very much for your reply. However, in my case I was not really deploying something, but I get your point. > I have not seen a bug report somewhere to php, but its possibly a question > if it should be considered a bug or not. Yep, this is the question I hoped would be answered on internals. > There are settings to trigger a re-evaluation which the links describe, > and its also possible to call opcache_reset() for example. This is just a workaround, which I used anyway. If the culprit is a combination of opcache and realpath caching, it should still be mentioned somewhere in the docs. In my case, it was rather an edge case and I usually would not run into this problem. It is something I have noticed though, and I hoped I'd get some feedback from the developers. Thanks again for the reply and the links. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
signature.asc
Description: OpenPGP digital signature
