04.11.2014 o 10:35 Jussi Laako <[email protected]> wrote:
On 3.11.2014 10:52, Maciej Wereski wrote:
Since systemd v212 DBUS_SESSION_BUS_ADDRESS is set per user in
[email protected]. As long as xserver is pulled by default.target in
/usr/lib/systemd/user, it will have DBUS_SESSION_BUS_ADDRES set.
That would be generally bad idea, because it may lead to unexpected
start of Xserver or inability to run more than one X session with the
same user.
This kind of stuff should be launched inside session, not as a user
service (singleton per logged in user, regardless of number of logins).
This is one of the areas were are now trying to clean up in Tizen where
there is horrible mess between user and session services!
Well, currently user-session-launch uses PAM and logind to login user.
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.
Having this set in one place is better solution, than setting this in
multiple service files, scripts and other environment files. What's more
one bus per user may also has it benefits. In the future, when we'll stop
abusing systemd --user to launch and every session has it's own dbus
session, it'll be easier to change that in one place.
regards,
--
Maciej Wereski
Samsung R&D Institute Poland
Samsung Electronics
[email protected]
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
