Thanks - I follow you now.
I've reproduced this behaviour on 2.2.14-5ubuntu8.11 (Lucid),
2.2.22-1ubuntu1.3 (Precise) and 2.2.22-6ubuntu5 (Saucy).
But I can't find any regression as you describe.
The init script does have access to the owner and group configured in
/etc/apache2/envvars, so I think it may be a reasonable Wishlist item to
have the init script automatically fix up /var/lock/apache2 for you.
This is something that is best submitted as a Debian bug, and then if
fixed there we can adopt the fix in Ubuntu on the next merge.
If this is a regression, then please provide an example of how to
reproduce the problem not occurring in an older release.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: apache2 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1177140
Title:
Apache not removing lock directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1177140/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
