On 17.11.2014 12:10, Dominig ar Foll wrote:
those session are created for different users.
What I ask is to not get multiple session for the same user.
Where is that officially documented?
TLM is used also for creating other than user sessions. For example on
default IVI configuration it is used to create session for the system
renderer. This session completely different from a normal user session
and for example at the moment doesn't have dbus session bus at all
(pam_systemd is not called for it).
I can also imagine number of use cases where it would be necessary to
support logging in the same user twice in IVI system. For example vendor
could like to login driver's userid by default on dashboard and center
console, starting the dashboard GUI and center console home screen
sessions respectively. And allow switching user of the center console
without affecting driver's session on the dashboard. Such vendor can
certainly make sure that their dashboard implementation can co-exist
with their homescreen implementation.
I don't want to artificially limit usability of the software components,
especially since Tizen is not a product but just a platform instead. It
is up to a product vendor to decide what limitations they want to
implement and they can implement it at the level they see suitable. If
they want to limit it for the graphical user session logins, then one
place would the the login application that talks to the TLM API. We only
ship engineering command line utility and engineering EFL GUI for
performing these operations. But those are certainly not intended for
any product use.
TLM itself doesn't know which sessions are "user session" and which are
"system sessions" for example. (and yes, any daemon you run from
systemd's "system" category also holds a session from kernel's perspective)
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
