** Description changed: Binary package hint: apache2.2-common I'm running apache2.2 (package apache2.2-common 2.2.3-3.2build1) as a webdav server on feisty (amd64). According to the apache documentation, http://httpd.apache.org/docs/2.2/mod/mod_dav_fs.html, the directory containing the lock database must be readable and writable for the user and group under which apache is running, i.e. www-data. The lock database is by default set to DAVLockDB /var/lock/apache2/DAVLock in /etc/apache2/mods-available/dav_fs.conf $ mount | grep lock varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) This is am ramdisk, right? So /var/lock/apache2 is created at every time the machine boots by /etc/init.d/apache2, the owner and group are set to root. line 97: [ -d /var/lock/apache2 ] || mkdir -p /var/lock/apache2 This ownership prevents apache from accessing the lock database, write access to the dav enabled folders is impossible. I have changed the line above in /etc/init.d/apache2 to 97: [ -d /var/lock/apache2 ] || { mkdir -p /var/lock/apache2; chown www-data:www-data /var/lock/apache2; } Is it a good idea to fix it like this? Thanks, Christian + + TESTCASE: + + Setup: + 1.Install apache2: + sudo apt-get install apache2 + + 2.Enable dav_fs: + sudo a2enmod dav_fs + + 3.Setup dav in default configuration (/etc/apache2/sites-enabled/000-default): + Add the following configuration just before </VirtualHost> + + <Location /> + DAV On + </Location> + + 4. Reboot the machine: + sudo reboot + + Test: + Using the cadaver web dav client on the command line: + + $ cadaver http://localhost/apache2-default/ + dav:/apache2-default/> lock index.html + Locking `index.html': failed: + 500 Internal Server Error + + Expected result: + $ cadaver http://localhost/apache2-default/ + dav:/apache2-default/> lock index.html + Locking `index.html': succeeded. + + When testing the updated package, make sure to reboot the machine before + testing.
-- /var/lock/apache2 has wrong owner and group for webdav https://bugs.launchpad.net/bugs/129920 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
