On Fri, Dec 30, 2022 at 12:59:19AM -0500, Nico Kadel-Garcia wrote: > On Wed, Dec 28, 2022 at 7:01 AM Ralf Corsépius <rc040...@freenet.de> wrote: > > > > Am 28.12.22 um 11:49 schrieb Peter Boy: > > > > > > It is a good idea to make the timeout configurable. But the default > > > timeout for servers must remain unchanged. > > > > My problem is not "defined timeouts" it is systemd delaying shutdowns > > for no obvious reasons. > > You've apparently not encountered the corruption of a database under > heavy load where the cache where swapspace has not yet been propagated > to disk. Imagine a server running a lot of virtual machines for an > image of what an overly aggressive shutdown timeout can do to your > otherwise stable systems.
This sounds serious, and this is the situation in which default setting is not correct, no matter if its 15 seconds or 120 seconds. The database and VM services should define own timeout (it goes from 0 to infinity, plenty of values to choose from). -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) _______________________________________________ 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
