On Fri, 23 Dec 2022 at 08:26, Vitaly Zaitsev via devel < [email protected]> 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? 1. Set default at 15s or something short. 2. 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 -- > Sincerely, > Vitaly Zaitsev ([email protected]) > _______________________________________________ > devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
_______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
