On Fri, May 27, 2016 at 5:03 PM, Paul Wouters <paul(a)nohats.ca> wrote:
If there is a systematic
problem of badly written code leaving orphaned code running when
a user logs out, then that broken code should be fixed instead of
adding another layer of process management. systemd is not capable
of interpreting the user's intent.
That isn't working. Users are constantly running into restart and
shutdown delays. Troubleshooting this to find out what process is
holding things up is totally non-obvious. Identifying the process is
half the problem, and then getting it fixed and released to Fedora can
be months, by which time some other process is affected.
The latest one I've run into  I can't figure out what the culprit
is. All processes have a status of S or derivative thereof. Clearly
it's something in session-c1.scope since in the end that's what
systemd forcibly kills. But it only does that after 90 seconds, which
is just untenable. And as you can see, does the user blame gnome-shell
because that's where the hang occurs? Or is it gdm because that's
what owns the scope that won't quit? Or is it some process within that
scope that's the problem, and if so how to find it? Non-obvious.