Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session
Santiago Vila
sanvila at unex.es
Tue May 31 17:53:43 BST 2016
Package: libpam-systemd,login
Dear maintainers:
Since I upgraded to stretch, logcheck sends me messages like this each
time I do "su -" to become root:
Security Events for su
=-=-=-=-=-=-=-=-=-=-=-
[...] mymachine su[4887]: pam_systemd(su:session): Cannot create session: Already running in a session
Apparently, "su" is doing something which is not necessary, or in a way
which is not optimal for systemd, or maybe pam_systemd is too picky
about what "su" does.
I don't know which of the two packages is to blame for this, so
I'm filing this report against both, libpam-systemd and login,
in the hope that you both can reach to an agreement about that.
If it happens that everything is ok and working as expected, then
it would be nice to have anyway some rule in /etc/logcheck to avoid
the message being considered as a "security event".
Thanks.
More information about the Pkg-systemd-maintainers
mailing list