Hi list, On Wed, Jan 22, 2014 at 10:24:24AM +0100, Djalal Harouni wrote: > On Thu, Jan 16, 2014 at 11:19:08AM +0100, Djalal Harouni wrote: > > On Thu, Jan 16, 2014 at 06:01:58AM +0100, Zbigniew Jędrzejewski-Szmek wrote: > > > Indeed, in a container (without your patches), sessions remain in > > > "closing" state. But with your patches, systemd --user instance is > > > started and killed immediately during login. Not good either :) > > Ok, ouch! > It seems that the systemd --user instance is killed without my patches! > > Systemd git will confirm it. > > Ok, after some thoughts and source code analysis, I came to the > conclusion that in order to correctly clean session and user state > files, we need: > > a) Improve session_check_gc() and user_check_gc() by using the session > and user states. This implies b) > > b) Make sure that the state of the session and the user is always > correctly set. Just to let you know that I've a v2 series, a more complete one.
I'll clean it and send it, thanks! -- Djalal Harouni http://opendz.org _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
