[systemd-devel] user at .service doesn't stop on logout

[Chris Murphy]

On Dec 10, 2013, at 11:19 AM, Lennart Poettering <lennart at poettering.net> wrote:

> On Mon, 09.12.13 20:56, Thomas Bächler (thomas at archlinux.org) wrote:
> 
>> In systemd 208 and latest systemd git, every user gets a new
>> user at .service instance when they login. However, when their last session
>> exits, that service is not terminated.
>> 
>> After a few weeks of uptime on one of my servers, dozens of
>> user at .service units are running, belonging to users that logged in weeks
>> ago and haven't been seen since. Is this really the intended behaviour?
>> 
>> Random screenshot: https://paste.xinu.at/RZn/
> 
> That service should be reference counted by the sessions of the users
> logging in. I should hence go away if the users successfully log out
> from their last session.
> 
> Your screenshot shows the user as "closing". Usually that state is only
> entered if there are processes still around of the user even though the
> user logged out (such as screen). That's at least the theory, but there
> might be some bug left.
> 
> Do you see any session of that user still around when you run into this
> issue?

At least in the Fedora 20 case that I'm running into with installed systems there is only one session, which is the session used to execute the reboot. I also get this occasionally with all live desktop builds so far during Fedora 20 testing, when rebooting after install, but I haven't checked if there are any other users logged in, I wouldn't expect that to be the case as I have sole control over that system. It is somewhat transient.

https://bugzilla.redhat.com/show_bug.cgi?id=1023820


Chris Murphy