On Wed, 2013-10-16 at 12:29 +0300, Jussi Laako wrote: > On 15.10.2013 20:18, Schaufler, Casey wrote: > > When the session is created the information about the session is > available. Otherwise, you can't create the session. At the time the > session is created this information is sent to AMD. We know it is > correct, because we just used it to create the session. When a launch > request is made the session information that was used to create the > session is available because to was explicitly sent to AMD. > > Some of the information for the session is built up as part of session > initialization, such as dbus session bus address. This is not known > before the dbus-daemon is started, because it is created by the daemon > at startup time.
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. Of course, there might be other examples where part of the session env setup is done by user processes as part of the session startup. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
