Bug#458085: apache2.2-common: wrong permissions on /var/lock/apache2

On Saturday 29 December 2007, Gabor Gombas wrote:
> On Sat, Dec 29, 2007 at 02:41:03AM +0100, Stefan Fritsch wrote:
> > It was a bit unfortunate that the line had to be introduced in a
> > stable point release and caused a behaviour change, but it was
> > necessary to fix a different bug.
>
> You could at least test for the existence of /var/lock/apache2 and
> create it only if it's missing. If /var/lock/apache2 already exists
> just leave it alone and do not change its ownership.

It was necessary to chown an existing /var/lock/apache2 to fix broken installations. It would have been possible to only do the chown if the owner was root, but I did not think of that when I prepared 2.2.3-4+etch3. But since the next update of etch (r3) will only be released in two months at the earliest, it does not make sense to change this in etch. People who are upgrading to 2.2.3-4+etch3 and are affected by this problem will need to change their init script _now_. People who do a new install won't experience a behaviour change, so there is no problem in this case.

> OTOH it could be nice to have an "apachectl dump" command that
> dumps the parsed apache configuration so scripting would be
> easier...

Yes, but I don't think this would be easy to implement.

Stefan

-- 
To UNSUBSCRIBE, email to debian-apache-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org