On Mon, February 27, 2012 6:46 pm, Christopher Jones wrote: > > > On 02/27/2012 01:12 PM, William A. Rowe Jr. wrote: >> On 2/27/2012 6:58 AM, jpauli wrote: > >>> Recently we had a bug with the new Apache 2.4 API where apxs >>> doesn't answer >>> about the MPM configuration anymore, leading to a ZTS build by >>> default. >>> This bug has now been fixed, was >>> https://bugs.php.net/bug.php?id=61172. >> >> Wrong fix. Out of the box you don't know which mpm may be loaded, >> because >> the mpm is now loadable (although a full daemon stop/start is >> necessary). > > Can you expand & explain this, with an eye to resolving 61172? > Are you saying Apache 2.4 'httpd -M' might not return the mpm?
If I'm reading this correctly: apxs runs at PHP compile time and "reads" mpm from httpd.conf Apache is started, probably with that mpm, and then a different mpm is loaded and apache is re-started, maybe even with graceful, for real fun. mod_php has no knowledge of the "new" mpm, because the mpm choice was compiled in at apxs time. -- brain cancer update: http://richardlynch.blogspot.com/search/label/brain%20tumor Donate: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
