Public bug reported:
Binary package hint: apache2.2-common
It looks like /etc/init.d/apache2 has a one-liner to fix missing
/var/lock/apache2 directory. This is useful for example when /var/lock
is on tmpfs. However, the init script doesn't change the ownership of
newly created /var/lock/apache2 directory.
Here's a snippet from /var/lib/dpkg/info/apache2.2-common.postinst:
# Make sure /var/lock/apache2 has the correct permissions
if [ -d /var/lock/apache2 ]; then
chown www-data /var/lock/apache2
fi
But the /etc/init.d/apache2 does only the directory creation:
[ -d /var/lock/apache2 ] || mkdir -p /var/lock/apache2
I think copying (or even moving) the "if [ -d ..." block from the
postinst script to init.d script would be the correct fix.
For example dav_fs tries to create a lock file, but fails:
[Mon Apr 23 14:53:27 2007] [error] [client 127.0.0.1] The locks could not be
queried for verification against a possible "If:" header. [500, #0]
[Mon Apr 23 14:53:27 2007] [error] [client 127.0.0.1] Could not open the lock
database. [500, #400]
[Mon Apr 23 14:53:27 2007] [error] [client 127.0.0.1] (13)Permission denied:
Could not open property database. [500, #1]
I'm currently running a fresh AMD64 Kubuntu Feisty installation.
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
/etc/init.d/apache2 doesn't do "chown www-data /var/lock/apache2" after
directory creation
https://bugs.launchpad.net/bugs/109250
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
