On Wed, Dec 28, 2022 at 9:13 AM Peter Boy <p...@uni-bremen.de> wrote: > > > > > Am 28.12.2022 um 13:34 schrieb Neal Gompa <ngomp...@gmail.com>: > > > > On Wed, Dec 28, 2022 at 7:25 AM Frank Crawford <fr...@crawford.emu.id.au> > > wrote: > >> > >> ... > >> > >> I'd also note that this has always been configurable, it is just now > >> suggesting a different value from the default. > > > > I would also suggest that if you're shutting down/rebooting a server, > > then you really want that to be done sooner rather than later, so > > stuff getting killed as it shuts down if it doesn't do it normally > > after SIGTERM is probably fine, because they're likely hung. > > > > Waiting a half hour for a system to reboot is not acceptable. > > Indeed, but it is not acceptable because the configuration of the timeout is > too long, but because there is probably something earnestly going wrong. And > as a server admin, I would like to decide myself to wait patiently and hope, > to evaluate the issue, or to pull the plug. I don't want to leave that to a > stupid timeout. > > > > 15 or 30 seconds is probably fine, even for servers, because of the > > nature of how systemd processes this timeout. It's per service being > > shut down, rather than a global timeout. > > Yeah, *probably* fine, maybe not. We don’t know, just guess. And as the > saying goes: better safe than sorry. > > And the 2 mins are empirically obviously a safe solution. >
Is it? If the end result is the same, it doesn't matter whether it's 30 seconds or 2 minutes. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
