24-Oct-98 18:14 you wrote:
> Now with DSO you're happy: You can combine 1.) and 2.). Why? Because
> you just make one Apache installation with mod_ssl as a DSO. And
> then you you an additional
> <IfDefine SSL>
> LoadModule ssl_module libexec/libssl.so
> </IfDefine>
> in your httpd.conf file. Now you can start the 70% non-SSL-aware httpds via
> "httpd" and the remaining 30% (SSL-aware) httpds with "httpd -DSSL". Bingo!
> Only one Apache installation required and no RAM penalty for the 70% of your
> non-SSL servers.
Hm.
1. Why you need two httpd servers in first place ?
2. How much is memory penalty for not-used mod_ssl ?
So I'm not sure that this will help ISP's at all (you still must reinstall
apache!) while this will be help distribution creators (like me :-)...
> More information comes when the DSO stuff is available with 2.1b7 for your own
> testing pleasure. But mainly the only difference you will see is a single
> "--enable-shared=ssl" inside the INSTALL file. Anything else is automatically
> configured. ;-)
It's not good. For distribution creators will be FAR better to have separate
patch file for Apache and separate mod_ssl distribution complable via apxs ...
BTW problem with mod_perl is solved:
--- mod_perl.c
+++ mod_perl.c
@@ -690,7 +690,7 @@
Apache__ServerStarting(FALSE);
#if MODULE_MAGIC_NUMBER >= MMN_130
if(perl_module.dynamic_load_handle)
- register_cleanup(p, NULL, mp_dso_unload, NULL);
+ register_cleanup(p, NULL, mp_dso_unload, null_cleanup);
#endif
}
It was 100% mod_perl problem and from patch itself you should see (as clever
programmer) why I had this program while you not :-)) It's was not
platform-dependant problem as well...
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
