summaryrefslogtreecommitdiff
path: root/src/python-systemd/_journal.c
diff options
context:
space:
mode:
authorDjalal Harouni <tixxdz@opendz.org>2014-02-13 18:31:43 +0100
committerLennart Poettering <lennart@poettering.net>2014-02-13 21:07:13 +0100
commitb58b227a53ee2b9feba8433a1558b51132ffb18b (patch)
tree018caa5b7e72dcc1a04becfd203cc11598029c2d /src/python-systemd/_journal.c
parent24fb111207566f3bb33c6438714fb5df44ed4305 (diff)
logind: make sure to terminate systemd user on logouts
Currently if the user logs out, the GC may never call user_stop(), this will not terminate the systemd user and (sd-pam) of that user. To fix this, remove the USER_CLOSING state check that is blocking the GC from calling user_stop(). Since if user_check_gc() returns false this means that all the sessions of the user were removed which will make user_get_state() return USER_CLOSING. Conclusion: that test will never be statisfied. So we remove the USER_CLOSING check and replace it with a check inside user_stop() this way we know that user_stop() has already queued stop jobs, no need to redo. This ensures that the GC will get its two steps correctly as pointed out by Lennart: http://lists.freedesktop.org/archives/systemd-devel/2014-February/016825.html Note: this also fixes another bug that prevents creating the user private dbus socket which will break communications with the user manager.
Diffstat (limited to 'src/python-systemd/_journal.c')
0 files changed, 0 insertions, 0 deletions