On Tue, 21.01.14 09:33, Holger Schurig (holgerschu...@gmail.com) wrote:
Hi,
on my systemd v208 + many patches from the Fedora 21 source RPM i get
TWO error messages in my journal when I login as root:
09:27:58 systemd-logind[118]: Failed to start unit user@0.service:
Unit user@0.service
Hi,
on my systemd v208 + many patches from the Fedora 21 source RPM i get
TWO error messages in my journal when I login as root:
09:27:58 systemd-logind[118]: Failed to start unit user@0.service:
Unit user@0.service failed to load: No such file or directory.
09:27:58 systemd-logind[118]: Failed
Am 21.01.2014 09:33, schrieb Holger Schurig:
on my systemd v208 + many patches from the Fedora 21 source RPM i get
TWO error messages in my journal when I login as root:
09:27:58 systemd-logind[118]: Failed to start unit user@0.service:
Unit user@0.service failed to load: No such file or
On Tue, Jan 21, 2014 at 1:01 AM, Thomas Bächler tho...@archlinux.org wrote:
So, I'd mask systemd-logind.service and remove pam_systemd.so from the
PAM configuration (I think it's set so that failure is ignored anyway,
but removing it should still be safer).
It will detect a lack of
Thomas,
logind in conjunction with udev's tagging also sets some device ACLs
correctly, which I like. I also like that I can have a protection to
not reboot my system while a user is active. So I'm not ready to get
rid of logind completely.
I'd actually have used user sessions if starting a
I'd actually have used user sessions
Not sure if I'd translate to I would have actually used. But that
is what I meant :-)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, Jan 21, 2014 at 1:01 PM, Thomas Bächler tho...@archlinux.org wrote:
Am 21.01.2014 09:33, schrieb Holger Schurig:
on my systemd v208 + many patches from the Fedora 21 source RPM i get
TWO error messages in my journal when I login as root:
09:27:58 systemd-logind[118]: Failed to start
