On Mi, 11.01.23 16:35, Zbigniew Jędrzejewski-Szmek (zbyszek@xxxxxxxxx) wrote: > We have thousands of systemd services in Fedora. To "just add timeouts > to things that take too long" would mean updating them individually. > (Or maybe only some, but we don't really know which ones.) > This is never going to happen, it's just too much work, and there is > no clear clear understanding if it is "safe" for any specific service. > > Instead, the idea is to attack the problem from the other end: reduce > the timeout for everyone. Once this happens, we should start getting > feedback about what services where this doesn't work. Some services > legitimately need a long timeout (databases, etc), and for those the > maintainers would usually have a good idea and can extend the timeout > easily. Some services are just buggy, and with the additional visibility > and tracebacks, it should be much easier to diagnose why they are slow. > > Approaching the problem from this side is much more feasible. We'll > probably have to touch a dozen files instead of thousands. Just to say this cleary btw: when we introduced the time-out initially we were coming from sysvinit where no such time-out existed at all. Hence we picked a conservative (i.e. overly long) value to not upset things too badly. And yes, some people were very much upset we now defaulted to a time-out. If we'd start from scratch without sysvinit heritage, I think we would have started with something much much lower right-away. It appears to me fedora is considering switch to that now, and I certainly think that would make a lot of sense. Anyway, if fedora now wants to lower the default setup, then I certainly sympathize. I think a policy of "aggressive time-out by default, individual opt-outs per-service" is a better policy for a stable OS than the current "conservative time-out by default, individual opt-in per-service for something more aggressive". So yes, lowering the time-outs by default would make sense to me, but of course, people will be upset... Lennart -- Lennart Poettering, Berlin _______________________________________________ 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