Re:PHP 4.0.0 and mod_dav 0.9.17-1.3.6 and Apache 1.3.12

Dear Fellow PHPers. The following is a summary of problems we've had installing mod_dav with Apache, so it's sort of a "pre-PHP" report -- but, given conflicting postings to this list about PHP and mod_dav, would like to know if PHP 4.0.0 and mod_dav 0.9.17-1.3.6 are going to work together or not using Solaris 2.6/gcc 2.95.2. Anyone have experience with this? Cheerio, Rick Rodgers & Ziying Sherwin ------------------------------------------------------------------------ Summary of Problems installing mod_dav 0.9.17-1.3.6 with Apache 1.3.12 We installed mod_dav 0.9.17-1.3.6 with Apache 1.3.12 under Solaris 2.6. We installed mod_ssl prior to mod_dave, so patches from both are present in our Apache code set. We also want to be able to use mod-dav in conjunction with PHP 4.0.0 (though that is not addressed here, and there is conflicting information in the PHP developer's mail lists as to whether this will work or not; we will post this to the appropriate lists/reporting engines for Apache, mod_dav and PHP). According to the installation instructions, there are two ways to install mod_dav with Apache: 1) As a dynamically loaded module using the "apxs" tool. 2) As a statically linked part of the Apache executable. (We can provide *fully detailed* installation instructions for anyone who would find them helpful). Here is a summary of our results with both methods: DYNAMICALLY LOADABLE MODULE For the case of building a dynamically loaded module, we installed Apache 1.3.12 first, and then used: ./configure --with-apxs=/site/subsys/www/apache/bin/apxs \ --with-expat=/site/subsys/www/expat_1.1 to configure, built the system, and installed it. After the libdav file was copied into apache/libexec and httpd.conf was updated, we edited the httpd.conf file as instructed, adding the following lines to enable DAV, lock the database, and set the lock timeout minmum: DAVLockDB /site/subsys/www/apache_1.3.12/var/DAVLock DAVMinTimeout 600 <Location /site/subsys/www/apache_1.3.12/htdocs/dav> DAV On </Location> When we installed it the first several times, we would start the script with: apachectl startssl and (on some trials) with apachectl start but the script would fail with an error message complaining about not recognizing "DAVLockDB". In our most recent installation, apache starts (this is a deep mystery, as we did nothing different!). Since we have no way to test WEBDAV itself, we do not know whether it really works. STATICALLY LINKED When building a statically linked version, before installing Apache 1.3.12, we configured mod_dav: sh ./configure \ --with-apache=/site5/SOURCE/INSTALL/web_kit_1.0/apache_1.3.12 \ --with-expat=/site/subsys/www/expat_1.1 then we built and installed the package, which copied some necessary files into the [...]/apache_1.3.12/src/module/dav directory. When we configured the Apache package, we added an extra line to the configure command: --activate-module=src/modules/dav/libdav.a Then we installed the apache package. The build and install steps went smoothly. The apachectl script runs without complaint, but there is no apache process running moments later. A pid entry has been created in [...]/apache_1.3.12/logs/httpd.pid, suggesting that httpd started and then died without an error message, but the actual process with that pid is not running. FINAL STATE OF AFFAIRS We made a final attempt to install mod_dav both ways, following the same procedure we had earlier, and for some strange reason, both methods worked! Here then are our current questions: 1) How can one test mod_dav? Is running the Python script util/regress the only currently available way? It would seem that a simple test of some sort, with documentation as to the normal outcome, ought to be part of the installation instructions. 2) Anyone have thoughts as to why our final installations *worked*? This is deeply mysterious to us.