[Dev] Tizen 3.0 proposal for fixing OSP/WRT/Core hard-coded UID issue

Baptiste DURAND baptiste.durand at eurogiciel.fr
Wed Oct 16 10:38:48 GMT 2013

Hi all ,

I have just investigated on the following question :
/But are we sure we don't need to support multiple sessions per user? //
Here is my results:

  * First,

Following DBUS Documentation,
There is only 1 dbus session per user login.
"The other instances are created one per user login session. These 
instances allow applications in the user's session to communicate with 
one another. "
 > http://dbus.freedesktop.org/doc/dbus-tutorial.html

So DBUS is designed to get only 1 dbus session per USER.

  * Second,

For Deamons there are  two ways to  get session adress:
  by getting DBUS_SESSION  environment variable (used if  it an abstract 
socket => 
by knowning the dbus adress : this is the case in tizen: each user have 
a dbus session socket stored : /run/<User>...

  * Finally, *the dbus service system (/usr/share/dbus-1/services/)
    should be hard to manage*, because this system allow to launch an
    app that provides a specific dbus interface when a process request
    it, througth the dbus session.

In my opinion, it is probably *"*not" a good idea to get multiples dbus 
sesssion per user login.


Baptiste DURAND

Le 16/10/2013 11:59, Jussi Laako a écrit :
> On 16.10.2013 12:41, Patrick Ohly wrote:
>> This might not be the case for this particular example: on the IVI image
>> using the systemd user session management, the session D-Bus socket
>> address is hard-coded per user. Initially, systemd listens on that
>> address and then starts the dbus-daemon on demand when a client tries to
>> connect to D-Bus via that socket.
> OK, on openSUSE (also using systemd) that is the case only for system 
> bus. Session bus still runs with "dbus-daemon --fork --print-address 
> --session" and has random dbus session bus address.
> Fixed per user address may become tricky in case there are more than 
> one user session per userid.
> With our current plan, there would be a separate guest user per seat 
> so it shouldn't become an issue. But are we sure we don't need to 
> support multiple sessions per user?

> _______________________________________________
> Dev mailing list
> Dev at lists.tizen.org
> https://lists.tizen.org/listinfo/dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131016/7079dd70/attachment.html>

More information about the Dev mailing list