On Fri, 2022-12-30 at 00:59 -0500, Nico Kadel-Garcia wrote: > On Wed, Dec 28, 2022 at 7:01 AM Ralf Corsépius <rc040203@xxxxxxxxxx> > 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. > I should ask here, have you timed how long you need the shutdown to be? Is the current default of 90 sec between progressively stronger signals sufficient? Also, given all these complaints about shortening the timeout, how many people know or have got around to changing either the default or the timeout for a specific service? This is all configurable (and yes, I have previously changed the default, because I felt it was too long). However, I even found out while investigating this email, that it is possible for a service to ask for more time on the fly, although it does take coding with the appropriate systemd API. I would suggest reading the man page "systemd.kill" for a better idea on what actually happens and what is possible. Regards Frank _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
