Am 2017-05-09 um 20:35 schrieb Lennart Poettering: > On Tue, 09.05.17 17:06, Jakob Schürz (wertsto...@nurfuerspam.de) wrote: > >> Hi There! >> >> I have two services running in systemd --user, which should only be >> startet for login-users. >> If i put the service-file by a deb-package in /usr/lib/systemd/user, the >> service will also be started for Debian-exim, Debian-gdm and other users >> with a UID below 1000. And this is not "good"... > > These users should not have a PAM session normally, and hence no > logind session either, and hence no systemd --user instance > either. There's something really strange if you actually do get PAM > sessions for these... Any idea why you get them?
I have no idea, why this users get a PAM-Session. Now i can see there is also a systemd --user process for debian-security-support: Jul 25 23:54:49 aldebaran systemd[1]: Starting User Manager for UID 137... Jul 25 23:54:49 aldebaran systemd[6366]: pam_unix(systemd-user:session): session opened for user debian-security-support by (uid=0) Jul 25 23:54:49 aldebaran systemd[6366]: Listening on Sound System. Jul 25 23:54:49 aldebaran systemd[6366]: Listening on GnuPG network certificate management daemon. Jul 25 23:54:49 aldebaran systemd[6366]: Started mkbackup-userdir.path. Jul 25 23:54:49 aldebaran systemd[6366]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Jul 25 23:54:49 aldebaran systemd[6366]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Jul 25 23:54:49 aldebaran systemd[6366]: Listening on GnuPG cryptographic agent (access for web browsers). [...] I don't know, why this session ist startet for the user with UID 137 I get this session every time on "dpkg-reconfigure debian-security-support" Jakob _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
