On Tuesday, June 2, 2020 2:05:01 AM MST Joe Orton wrote:
On Sat, May 30, 2020 at 11:13:35AM +0200, Zbigniew
> On Thu, May 28, 2020 at 03:53:26PM -0400, Ben Cotton wrote:
> > == Detailed Description ==
> > By default php-fpm is used for a few versions. mod_php is not
> > supported for threaded modules. mod_php usage also increases security
> > risk, sharing the same process than httpd.
> > Drop mod_php from php build. This will only affect user of httpd in
> > "prefork" mode, which will also use php-fpm.
> > php-fpm is already used but most users of httpd and nginx without any
> > issue.
> Based on the replies downthread, it seems that some people are still
> using it and want to keep it...
If the existence of non-zero user demand blocked removal of defunct
technology in Fedora I guess we'd still be shipping SysV init.
We made the switch from forked-httpd + mod_php to threaded-httpd +
php-fpm by default in Fedora 27, so we've spread this transition over
six full release cycles. We've had AFAIK *zero* bug reports about
making the default switch.
> Is mod_php a maintainance burder and/or a noticable installation
> overhead when not used? And if it is, would additional help with the
> maintainance that was offered make it easier to keep?
I'm not seeing any technical argument in this thread to support keeping
mod_php. If there were, that would be interesting, but otherwise I
think the package owner should be trusted and empowered to make this
If it's dropped, it wouldn't really be possible for me to make a mod_php
package to replace it due to the integration, so I can't really see a way of
keeping a compat package if it's removed, and keeping it around doesn't break
John M. Harris, Jr.