On 4.11.2014 12:40, Maciej Wereski wrote:
Well, currently user-session-launch uses PAM and logind to login user.
user-session-launch is wrong and should go away.
logind starts [email protected], which pulls default.target, which in turn pulls dbus.service for user. This has address always set to /run/user/%U/dbus/user_bus_socket. I haven't seen any other dbus session instances being run.
That's correct, dbus session bus, despite the name, is not session service, but user service, common to all sessions of a user. So if you have five sessions for user X, you still have just one dbus session bus running. When you log out the last session, the systemd --user goes down and dbus session bus as well. (every session increments refcount for systemd --user)
/run/user/%U is also similar, as per specification it is created when user X is logged in first time, and destroyed when last session of user X is logged out.
You can, if you like, configure session bus also to be independent for each session, with different bus address, but it will likely break certain set of services (and vice versa for the other case too).
This confusion between session and user services spans quite a number of open source desktop components.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
