Hi, 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. > This is quite fragile (because of includes, etc.) and we don't want to > do that. But it would make sense to either add a comment in > apache.conf that /etc/init.d/apache2 needs to be changed as well, or > to set the user via an envvar that can be used in both apache2.conf > and the init script. If the initscript does not unconditionally change the permissions on /var/lock/apache2 then I'm fine with a comment in apache.conf. OTOH it could be nice to have an "apachectl dump" command that dumps the parsed apache configuration so scripting would be easier... Gabor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
