On Wed, Jan 11, 2023 at 5:36 PM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > 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. Sound's terrible to me. Could we achieve this without knowingly breaking users' machine's shutdowns? Or annoying user base in general ? I can imagine a new standalone package, that only changes the timeout, and only people willing to test the short shutdowns would participate and install it? -- If somehow we end up with the terrible approach of "change crucial system-wide config and see what happens", could we at least do it step by step? Shortening the timeout by e.g. 10 or 30 seconds every Fedora release ? 30 minutes every half a year spent by copy-pasting the Fedora change from the last release sound's like a solid tradeoff for not gaining upset users. -- The different configuration for different Fedora editions doesn't sound right to me. The edition originally installed does tell us anything about any other software installed on that machine later. Hunting for well-known trouble-making services (regarding shutdown times) is a much cleaner approach. -- Is there any existing piece of software that can analyze the shutdowns and report the mean times and messages of each service / component ? I'd use it on my devices with problematic shutdowns. And I personally believe that strictly opt-in telemetry is a good way to gather user (telemetric) data. -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Wed, Jan 11, 2023 at 9:56 PM Michael Catanzaro <mcatanzaro@xxxxxxxxxx> wrote: > > On Wed, Jan 11 2023 at 11:48:27 AM -0800, Kevin Fenzi <kevin@xxxxxxxxx> > wrote: > > I do appreciate the change to do an abort on these units. Will that > > get > > reported via abrt? > > It should, yes, the same as any other crash. > > _______________________________________________ > 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 _______________________________________________ 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
