Whose responsibility is this? Should the Apache package somehow
know that it needs to restart itself? Should the libssl package
do something to cause Apache to restart? Should the unattended-
upgrades package know to restart Apache when libssl has been
upgraded?
I know there is a mechanism of some kind to cause daemons to
restart when libraries they use are being replaced; is that just
for libc updates, or something?
On Wed, 2023-02-08 at 14:01 +0000, Phil Endecott wrote:
Whose responsibility is this? Should the Apache package somehowHave a look into the needrestart package, which is suggested, but not required, by unattended-upgrades.
know that it needs to restart itself? Should the libssl package
do something to cause Apache to restart? Should the unattended-
upgrades package know to restart Apache when libssl has been
upgraded?
I know there is a mechanism of some kind to cause daemons to
restart when libraries they use are being replaced; is that just
for libc updates, or something?
On Wed, 2023-02-08 at 14:01 +0000, Phil Endecott wrote:
Whose responsibility is this? Should the Apache package somehow
know that it needs to restart itself? Should the libssl package
do something to cause Apache to restart? Should the unattended-
upgrades package know to restart Apache when libssl has been
upgraded?
I know there is a mechanism of some kind to cause daemons to
restart when libraries they use are being replaced; is that just
for libc updates, or something?
Have a look into the needrestart package, which is suggested, but not required, by unattended-upgrades.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (2 / 14) |
Uptime: | 03:16:12 |
Calls: | 6,666 |
Calls today: | 4 |
Files: | 12,212 |
Messages: | 5,335,697 |