https://issues.apache.org/bugzilla/show_bug.cgi?id=55897
--- Comment #6 from [email protected] --- Hi Jeff, Thanks very much for your response! Yes, we chose to use prefork mpm due to the use of libphp5.so (non-zts). We tested the zts version as well, but it showed some performance issues before. then, we decided to try the patch on prefork mpm first. We can surely extend this patch to worker and event mpm. We will use fcgi instead of libphp5.so for testing. Also, We will follow your suggestion to call apr_os_sock_get() in the follow up version of the patch. We will update this thread soon. Thanks! Yingqi (In reply to Jeff Trawick from comment #5) > Was this change tested with event or worker MPMs? Is the prefork MPM > desirable in this scenario due to the use of mod_php or some other > third-party module, or is there an issue with bundled modules that > necessitates the use of prefork, or is there some other reason for prefork? > > FWIW, you don't actually need an APR change to make the desired setsockopt > call. Call apr_os_sock_get() to get the file descriptor and call setsockopt > directly. That would make it easier for others to use the patch with > existing builds of APR. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
