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

Łukasz Stelmach l.stelmach at samsung.com
Wed Oct 16 13:59:20 GMT 2013


It was <2013-10-16 śro 11:59>, when Jussi Laako wrote:
> 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?

Current ideas for desktop are that there is one session for one user. If
user logs in on multiple seats this is still a single session as there
is quite some software that can't run more than once for a single user.

-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131016/77086e12/attachment.sig>


More information about the Dev mailing list