Hi,

>we're having almost the same problem: after the last update it's not
>possible to run both ssl and php4 modules.

AOL-user: me too :-)

I have been forced to install the stuff from scratch, using mod_ssl, mod_php
and apache directly from original locations.
Change into mod_ssl directory, do a (fix path to new apache sources)
./configure --with-apache=../apache_1.3.26/ --with-ssl=SYSTEM --with-mm=SYST
EM
change into apache-dir and do a
./configure --prefix=<you new
path> --enable-rule=EAPI --enable-module=all --enable-shared=max --<various
prefixes for SuSE directorys,
i.e. --libexecdir=/usr/lib/apache --sysconfdir=/etc/httpd etc...> --<suexec
if desired>
then build apache with make, copy the ssl-certs and httpd you are currently
using into a temp dir, make a backup of /usr/lib/apache and the
/sbin/init.d/apache script and uninstall all SuSE rpms. make install,
restore certs, .conf and init script, copy the missing modules from the
backup of /usr/lib/apache into the new libexec dir (use a cp -i, no
overwrite of new modules),
change into mod_php and do a configure with loads of options, make, make
install.

This is not quick but dirty, but all modules work for me. Take your time to
fix path, get the smaller module sources and recompile them if you wish. If
the httpd refuses to start, remove all <IfDefine> and <IfModule> statements
from httpd.conf and comment the stuff you're not using out (i.e.backhand,
dav), starting the server with simply ./httpd

Maybe this helps busted 7.0 users to switch to sources :-)

Ciao,
Dieter

---------------------------------------------------------------
Dieter Kirchner
Systemadministration BUPNET
+49 551 54707 62 D-Goettingen
http://www.bupnet.de
---------------------------------------------------------------

-- 
To unsubscribe, e-mail: suse-security-unsubscribesuse.com
For additional commands, e-mail: suse-security-helpsuse.com
Security-related bug reports go to securitysuse.de, not here

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]