Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12807 - [apache] please consider adding worker-mpm to build

Attached to Project: Arch Linux
Opened by eliott (cactus) - Thursday, 15 January 2009, 19:27 GMT
Last edited by Jan de Groot (JGC) - Saturday, 06 March 2010, 18:19 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Arch's apache config only has prefork-mpm packaged. It would be wonderful if Arch included the worker-mpm _in addition_, and just had a selectable option in an /etc/conf.d/httpd config var that /etc/rc.d/http utilized. Something like:

# uncomment the following to use the worker mpm.
# default is prefork mpm
# MPM_PATH=/path/to/httpd.worker

Thank you for your consideration.
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 06 March 2010, 18:19 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in 2.2.14-3. Use /etc/conf.d/apache to select your MPM.
Comment by Jan de Groot (JGC) - Friday, 16 January 2009, 08:13 GMT
Nice option, but be sure to think about possible consequences:
- modules built against the prefork server are not compatible with the threaded server and vice versa
- threaded server should have its own includefiles
- some modules aren't threadsafe anyways (php)
Comment by Pierre Schmitz (Pierre) - Friday, 16 January 2009, 12:11 GMT
Afaik we would need several apache packages and external modules have to be compiled for each of them. Maybe if we'll have split package support in makepkg there would be a sane way to do this.
Comment by eliott (cactus) - Friday, 16 January 2009, 16:15 GMT
Interesting.
Centos manages to get them both into a single package..with module sharing.
I don't see anything exceptionally magical in the rpm spec file for it.
Comment by Aaron Griffin (phrakture) - Friday, 16 January 2009, 16:19 GMT
I think the modules will work with either, at the code level, but some are incompatible due to threading issues (I remember this being documented somewhere)

Don't they have a module api for this very reason? Changing to a different MPM shouldn't suddenly use a different API, should it?

Loading...