On Thu, 3 Dec 1998, Ralf S. Engelschall wrote:
: And one more question: What's the reason you have to name the DSO
: mod_ssl.so instead of libssl.so? Because of the conflict with the "real"
: libssl.so?
Now I can't remember whether I answered this ... Because other shared object
modules are in general named "mod_*.so", and you enable it with `AddModule
mod_ssl.c'. Calling it `libssl.so' did not seem appropriate for a dynamic
module.
It does not conflict with the installed libssl, only because Apache normally
sends dlopen() an absolute pathname to find libssl (which precludes a
library search). In the NetBSD pkg version of apache, there's a special
hack to reverse this effect; a `LoadFile !libname.so' will ask dlopen() to
path search for the library.
: Ops, seems like I was too slow or you too fast. Last weekend I've added full
: APXS support to the distribution. I think this would make your life easier.
: When you're interesting you can test my APXS support.
I will be making use of it when I update the NetBSD pkg to 2.1.3, but it
will likely patch the makefile to call it `mod_ssl.so'. :>
--
-- Todd Vierling (Personal [EMAIL PROTECTED]; Bus. [EMAIL PROTECTED])
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
