I am trying to build apache1.3.12+mod_ssl+php as shared modules. A lot
of php extensions are also build as so (gd.so, mysql.so, oci8.so, xml.so
etc etc). When I start apache with mod_ssl disabled everything works
fine but if I enable it apche coredumps at startup. mod_ssl works fine
with php module disabled and visa versa. With some experimentation I
have found that if I change lines
AddModule mod_ssl.c
AddModule mod_php4.c
to
AddModule mod_php4.c
AddModule mod_ssl.c
then everything seems to work fine again...
I don't see all these problems if I don't activate mysql.so and oci8.so
extensions... And mysql.so was build --with-mysql=shared,/usr instead of
simple --with-mysql=shared. So that is a somewhat special build of
php... the only thing I see common for both mysql.so (build with
shared,/usr) and oci8 is that they are linked to pthread library...
While I have found the workaround (change the order of AddModule lines)
I am not sure that is the real solution...
Is it normal for apache to core dump depending on AddModule order?
Are there any recommendations for mod_ssl to make it the last module in
httpd.conf or something like that?
Are there any issues using modPhp and mod_ssl together?
Oleg
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
