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. > And as you asked: On my (bare metal) servers, Im am occasionally > experiencing delayed shutdowns in the order of several minutes. > > This is simply inacceptable! > > Ralf I'm assuming you have very busy filesystems, perhaps not well configured for their load. There databases that can be *really* corrupted by interrupted shutdowns, especially when the change has been written to the disk cache but not yet committed to disk. And some network services, like NFS, can take way too long to shut down gracefully, but risk the upstream server if clients are forcefully shut down. Nico Kadel-Garcia _______________________________________________ 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
