> Hmmmm.... when the apachectl isdn't patched correctly you should have seen an
> error under configure time. Because the whole configuration, building and
Yeah i thought tt the apachectl would be patched up as well.
> installation went fine for you, I guess you've messed up something. Are you
> sure the /apache_1.3.4/bin/httpd actually is the patches one? Run
> "/apache_1.3.4/bin/httpd -l", there should be a mod_ssl.c unless you used the
Listing:
http_core.c
mod_env.c
mod_log_config.c
mod_mime.c
mod_negotiation.c
mod_status.c
mod_include.c
mod_autoindex.c
mod_dir.c
mod_cgi.c
mod_asis.c
mod_imap.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_access.c
mod_auth.c
mod_setenvif.c
No mod_ssl.c!!!
> DSO facility. And the /apache_1.3.4/bin/apachectl script should really contain
> an startssl entry. But ok, the startssl is not important. It's nothing more
> than a wrapper around "/apache_1.3.4/bin/httpd -DSSL", so try to start it this
> way.
Looks ok. No mesg displayed.
Errrr, (most probably) stupid question: do i need to modify the httpd.conf to
incorporate the SSL stuff? Ive only done whatever the INSTALL file prescribes.
Next thing, nothing 'abnormal' shows up in the log files.
G.
--
Gilles Chong ([EMAIL PROTECTED], [EMAIL PROTECTED])
Systems Engineer, Internet Division
CSA Automated Pte Ltd, Singapore.
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
