Bug#868861: Mitigation

[Yadd <yadd@debian.org>]

Le 22/09/2021 à 13:54, Michiel Hazelhof a écrit :
> The complete and better walkthrough (systemd users only!), some parts
> might be redundant if you allready migrated to the proper systemd
> invocations:
> 
> This completely fixed the "There are processes named 'apache2' running
> which do not match your pid file which are left untouched in the name of
> safety, Please review the situation by hand. ..." warning (and the
> application kill that follows).
> 
> 0: systemctl disable apache2-instancename && systemctl stop
> apache2-instancename
> 1: delete /etc/init.d/apache2 and /etc/init.d/apache2-instancename
> 3: ln -s /usr/sbin/apache2 /usr/sbin/apache2-instancename
> 4: edit /usr/sbin/apache2ctl:
> - Find: HTTPD=${APACHE_HTTPD:-/usr/sbin/apache2}
> - Replace with: HTTPD=${APACHE_HTTPD:-/usr/sbin/apache2$SUFFIX}
> 5: systemctl enable apache2@instancename && systemctl start
> apache2@instancename
> 
> Important notices:
> 0: that your envvars in the apache config should change the suffix from
> @instancename to -instancename as is debians default (if not simply do
> the ln -s with @ instead of -)!
> 1: After every apache upgrade the /usr/sbin/apache2ctl mod needs to be
> performed again!
> 
> On Tue, 6 Jul 2021 09:47:09 +0200 Michiel Hazelhof <michiel@hazelhof.nl>
> wrote:
> 
>> Made two small tweaks to hopefully mitigate this behaviour:
> ... Do not follow this post anymore!

Hi,

could you push a merge request ?

Cheers,
Yadd