Hello,
On Friday, December 23, 2022 6:52:02 AM EST Tom Hughes via devel wrote:
On 23/12/2022 11:45, Naheem Zaffar wrote:
On Fri, 23 Dec 2022 at 08:26, Vitaly Zaitsev via devel <devel@lists.fedoraproject.org mailto:devel@lists.fedoraproject.org> wrote: On 23/12/2022 09:20, Mattia Verga via devel wrote: > I know this is way harder, but the right approach would be having a way > to tell systemd what processes can be killed and what other > processes > must not be forced off in any case, then display a user friendly message > which inform the user that the system cannot be forced off ATM "because > I'm doing this or that". In the worst case, the user can choose to pull > the plug themselves.
I agree. Terminating the PackageKit service while updates are being installed can result in a broken system.
Is there a way to be smarter about all this?
- Set default at 15s or something short.
- For services known to require longer (older pinephone modem firmware,
libvirtd), allow a larger timeout for that specific service only 3. For services that should NOT be terminated have a mechanism for them to not be cut off
Despite the title of this change I believe the proposal is only to change the default timeout and a service would still be able to set a different timeout in it's service file.
I wonder if this proposal should also include verifying that known problem services have an appropriate override?
-Steve