On Thu, Nov 04, 1999, Bart Locanthi wrote:
> hi, i have a question that so far i haven't found an answer to in the
> faqs or documentation..
>
> i'm configuring apache 1.3.9 with the usual load of modules plus
> mod_jserv in addition to mod_ssl.
>
> after configuring stuff as follows:
> 1) configur mod_ssl
> 2) make apache (-DEAPI shows up in all the modules compiles)
> 3) configure & make mod_jserv
> 4) configure & make mod_php3
>
> i get many warnings to the effect that "mod_X uses plain apache DSO and
> may *crash* under EAPI".
>
> the only module of interest that doesn't get this message is php3;
> mod_jserv *does* get it, and i very much want that one to work.
>
> so far i haven't seen any problems, but presumably the warnings aren't
> there without cause, so i'm wondering how one builds them to use EAPI.
> if possible.
>
> any suggestions? i would happily take a pointer and rtfm.
I never tried mod_jserv, so I don't know details about it. But the warnings
really means that mod_jserv wasn't compiled with -DEAPI or it has an unclean
module structure source (where the standard Apache macros are not used).
Additionally, you say you get "many" warnings. For which modules do you get
the warnings of which one not? Look inside mod_jserv.c or where mod_jserv has
its "module" structure definition. There has to be a STANDARD_MODULE_STUFF
macro call. If not, that the reason for the warnings. OTOH the warnings is
just a _warning_, it doesn't mean that the module _HAS_ to crash. But if it
(uncleanly) depends on some internals of Apache, it will certainly crash.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
