> Am 22.12.2022 um 19:29 schrieb Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx>: > > On Thu, 2022-12-22 at 18:44 +0100, Tomasz Torcz wrote: >> On Thu, Dec 22, 2022 at 12:35:54PM -0500, Ben Cotton wrote: >>> https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer >>> >>> This document represents a proposed Change. As part of the Changes >>> process, proposals are publicly announced in order to receive >>> community feedback. This proposal will only be implemented if approved >>> by the Fedora Engineering Steering Committee. >>> >>> == Summary == >>> A downstream configuration change to reduce the systemd unit timeout >>> from 2 minutes to 15 seconds. >> >> Great change, please do it! >> Also, sometimes after reaching the timeout, systemd extends wait by >> another 2 minutes (or 1m30). I wasn't able to find in the sources or >> documentation why this happens, but this behaviour should be blocked. >> Otherwise some services after 15s will get another 15, and then another… > > 15 seconds feels very aggressive to me. I can think of some cases, like > libvirtd automatically suspending or cleanly shutting down running VMs, > that might well take longer than that. Could we not go for 30 seconds? > Going all the way from 90/120 down to 15 seems pretty radical. Even though I am a bit late due to seasonal commitments, I would like to affirm a strong rejection of this change for the server variant on behalf of the server WG. The proposed limit of 15 secs is much to aggressiv, also the proposal of 30 seconds. Unfortunately, we do not have data on how long on average it takes for a productive server shutdown to terminate all VMs (with their own delays), all open database transactions, all service sessions, etc. But obviously the current time interval does not cause any striking problems. and is therefore OK for server. For a production server, a shutdown is a rare event and the main problem is not a period of 30 sec or 2 min, but the shutdown itself. And server admins are terribly conservative (and cautious) people, never change a working system unless there is a clear advantage. And this proposal brings no advantage at all for servers, only potential problems. It is a good idea to make the timeout configurable. But the default timeout for servers must remain unchanged. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy@xxxxxxxxxxxxxxxxx Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora docs team contributor and board member Java developer and enthusiast _______________________________________________ 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
