Just a random Debian user passerby; chiming in with my 2c...
On 11/12/23 18:51, Martin-Éric Racine wrote:
[...] This leaves me with two possible solutions: 1) No dh_install option. This will restart after upgrade (default since dh 10).
Assuming that I understand correctly (this option will start/restart dhcp post install - i.e. in postinst) then I think this would be the preferred path wouldn't it?
2) Add --no-stop-on-upgrade --no-restart-after-upgrade options. This will explicitely disable stop and restart actions.
Perhaps I'm missing something, but if the dhcpd binary is updated, don't we need to restart the service to ensure that we're using the updated binary?
In the case of a security update to dhcpd, wouldn't this leave the vulnerable service running until next reboot and/or manual service restart?
----In summary; option 1 seems like the "correct" path to me. But perhaps I'm missing something?
Regardless, thanks for your work on Debian. All you awesome volunteers rock! :)
Cheers, Jeremy
OpenPGP_signature.asc
Description: OpenPGP digital signature
