Your message dated Tue, 16 Feb 2021 22:51:54 +0100
with message-id
<CAJ2a_DcPr3xA+yfQqb+-6ntu43MK4r6=8bvvhv2n-2btj+5...@mail.gmail.com>
and subject line Re: Bug#982777: lighttpd: no restart of php-cgi children after
php update
has caused the Debian Bug report #982777,
regarding lighttpd: no restart of php-cgi children after php update
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
982777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982777
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.58-2
After a package upgrade of php the lighttpd spawned children of a
fastcgi setup are not restarted.
In case of a security update of php, one would still run the vulnerable version.
Please consider adding a trigger or the like to execute `service
lighttpd reload` after a php package upgrade.
--- End Message ---
--- Begin Message ---
> I strongly recommend using needrestart (which is very good at finding
> systemd services that need to be restarted after binary / library
> updates), which solves this problem in a very generic way.
>
> Also I strongly recommend not having webservers run/spawn backends -
> php-fpm is a way better alternative, and makes it quite easy to run a
> backend as a different user than the webserver (which, if you do care
> about security, you really should do).
>
> Not sure whether such trigger is implementable if php doesn't have a
> hook available for it anyway - and I doubt it is worth the effort.
Thanks, with php-fpm as backend it's not a problem.
--- End Message ---
