Re: systemd 230 change - KillUserProcesses defaults to yes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



OK so back to a specific example on Fedora 24 with a restart/shutdown
delay. User gdm owns session-c1.scope, and for some reason I can't
figure out, it won't quit on its own. So it enters a failed state
1m30s after I ask for a restart/shutdown. [1] I edited
/etc/systemd/logind.conf uncommented KillUserProcesses=yes and
rebooted. And at the next reboot, the problem still happens. While the
user session itself is gone, and lsof /home no long shows user chris
processes holding things up, user gdm still is causing the hang.

Since some other user process is the cause of the delay, and
apparently isn't subject to killuserprocesses, at least in this
instance it's not fixing (or papering over) this particular example of
a restart/shutdown delay. I don't know that this is a bug, but I went
ahead and filed it because it seems like killuserprocesses=yes should
apply to user gdm, because that user isn't an excepted user (unless
it's functionally the same as root, in which case the default
#KillExcludeUsers=root is probably why, and now we're just back where
we started where there are wayward processes that are causing restart
hangs and are difficult to identify.



Chris



[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1337307
[2]
https://bugzilla.redhat.com/show_bug.cgi?id=1341837
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux