Nate Bargmann:
Comparing the two systems I see that the one with the failure has
> 'console-kit-daemon.service' shown as "active (running)" and the one
> without the failure shows it as "inactive (dead)". The consolekit
> package is installed on each system, but '/etc/systemd/system'
> doesn't have anything related to consolekit on either machine.
You'll find it in /usr/lib/systemd/system, since it is a pre-packaged
service rather than your local administrative addition.
The systemd PAM plug-in instantiates from the user@.service template
when something attempts to authenticate with a user's credentials.
* http://freedesktop.org./software/systemd/man/pam_systemd.html
You're not the only person on the WWW to unknowingly have a
"user@9.service". The person who reported Debian Bug #758159 has one,
too. But then xe didn't notice that xe has a running
"serial-getty@ttyS2.service" with /sbin/agetty as process #1173. (-:
Your next stop is looking for that cron job, buried somewhere on your
system, that "su"s to user "news". Hint: It's part of slrn.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545e0e19.5080...@ntlworld.com