I am not an expert but I THINK this is the answer to your question. "make install" *will* overwrite /usr/local/apache/bin/httpd and the other binaries. /usr/local/apache/conf/*.conf will not be overwritten, instead additional sets with an altered filename will appear there. To preserve your 1.3.9 installation in case you have a problem, take a backup copy of /usr/local/apache/bin. Someone else who knows more than me will no doubt advise that following http://www.modssl.org/example/ is probably not a good idea - it really is just an example but you're probably missing some configuration options that you might want (eg. MM shared memory libary, DSO support) or (depending upon your home jurisdiction) might need (eg RSAref). See http://www.modssl.org/source/exp/mod_ssl/pkg.mod_ssl/INSTALL Regards >===== Original Message From [EMAIL PROTECTED] ===== >I currently have 1.39 with modssl working which was installed >according to the previous example set forth at >www.modssl.org/example/. If I again follow the procedure at >http://www.modssl.org/example/ to upgrade and the upgrade does >not go well--will the former version of Apache and modssl that I >currently have working still be available on the server or will the new >installation overwrite the old version ? > >If I do the upgrade, will it leave my existing httpd.conf file intact or >will I need to bring my current virtual host container entries, etc., >into newly created httpd.conf file ? > >Thanks for any advice. Bill > > > > > >______________________________________________________________________ >Apache Interface to OpenSSL (mod_ssl) www.modssl.org >User Support Mailing List [EMAIL PROTECTED] >Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
