[systemd-devel] [PATCH] cgroups: chown user slices

Oleksii Shevchuk alxchk at gmail.com
Thu Jul 11 13:56:38 PDT 2013

> pam_gnome_keyring needs to be in the pam stack for "systemd-shared" of
> course.

pam_gnome_keyring needs authinfo to unlock login keychain. Will that be
passed to new systemd instance? 

> Which environment would that be? 

When systemd fully runs session, than that will be full profile
environment + environment setted by login manager.

For example, DM should setup DISPLAY variable.

> Can you elaborate? Where exactly does it hang?

Some kind of debugging environment should be setted up before that. With
shared user instance user at .service hangs alot. Sometimes session scopes
rests in timeouts, when user session terminated without systemctl --user
exit. Looks like logind/pam_systemd doesn't kill something.  

I have some units in user session with KillMode=process. Maybe that matters

More information about the systemd-devel mailing list