Having experimented further, I've discovered more and more things that the 26.04 systemd configuration does that break other bits of PHP functionality in "curious and interesting ways".
(For example, you can't get the system memory with "free -m"; you can't invoke any binary that has a JIT (e.g. libreoffice for document- conversion); you can't access files under /home even with the relevant Unix file permissions). My conclusion was that this is the "final call" for mod-php, and that this is time to move to php-fpm. (which works perfectly for me). So, for what it's worth, my view is now that this shouldn't be a "bug fix", more a "release-note", to the effect that "mod-php is now known not to work properly, in multiple ways, with the new apache configuration". If there's any way to alert the administrator to this when they upgrade, it would be helpful, or even to put a logfile-warning when mod-php starts up. Hopefully others will now find this bug report and it will help with the context - because when I was googling this issue, all I found was advice to "set pcre.jit=0 to work around the warning message". Thanks for your time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2144455 Title: Apache's systemd option "MemoryDenyWriteExecute" breaks PHP JIT, under mod-php To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2144455/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
