On Thu, Dec 22, 2022 at 05:22:09PM -0500, Steve Grubb wrote:
> On Thursday, December 22, 2022 1:29:29 PM EST Adam Williamson wrote:
> > 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.
> 
> I run across this with some regularity. PackageKit is not installed on my 
> system. What I wished was that when there is a stall shutting down, a message 
> to the console or a dialog box explains who is holding up shutdown. If we 
> knew who was holding things up, bugs might get filed.

  But there already is such message! First "waiting for shutdown" with
unit name and a timer. Then, in the last phase there's also "wating for 
process:"
message.
  The problem is: at this points it is hardly debuggable. One cannot
start a new shell, sshd is off already, journalctl too. No way to gather
any information what's wrong with the process holding up shutdown. We
only get a name.  And usually you cannot reproduce the problem easy on
next shutdown.
  Maybe netconsole is still functioning at this point, but I doubt it.

-- 
Tomasz Torcz                        To co nierealne – tutaj jest normalne.
to...@pipebreaker.pl              Ziomale na życie mają tu patenty specjalne.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to