Jussi,
Yes, you're right: systemd --user is started in parallel of
user-session-launch which maintains the PAM (and logind) session.
Here's what I can see on a recent T:Common image when I run 'systemctl
status':
systemd (system)
└─user.slice
└─user-5003.slice
├─session-c2.scope
│ └─248 /usr/bin/user-session-launch seat0 5003 => opens session
└─[email protected]
├─369 /usr/lib/systemd/systemd --user
├─413 (sd-pam)
├─weston-user.service
│ └─854 /usr/bin/tz-launcher -c ...
├─dbus.service
│ └─722 /usr/bin/dbus-daemon --session ...
└─amd_session_agent.service
└─712 /usr/bin/amd_session_agent
IIRC, user-session-launch was introduced as a workaround, to avoid
opening systemd/logind sessions for any PAM service (ssh, su, login
...): it creates a specific service that would open a specific pam
session (user_session) which in turn will be the only PAM service to
call pam_systemd module that interacts with logind.
I don't pretend to say that it's the right way to do things, but
actually this has bad consequences: user services and user sessions are
mixed in a single concept.
I understand that user-session-launch should disappear: what's the big
picture then ? How (and when) will we get rid of this confusion between
user services and user sessions ?
Thx for feedback.
--
Stéphane Desneux
Intel OTC - Vannes/FR
gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726
On 04/11/2014 10:37, Jussi Laako wrote:
> On 3.11.2014 19:49, Stéphane Desneux wrote:
>> Technically, as long as Xorg is launched inside a user session it will
>> have the DBUS_SESSION_BUS_ADDRESS set by systemd, as explained Maciej
>> previously.
>
> "systemd --user" is NOT inside session, it specifically runs OUTSIDE the
> session as the user to provide services for all the user's SESSIONS.
>
> _______________________________________________
> Dev mailing list
> [email protected]
> https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
