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
'Twas brillig, and Simon McVittie at 20/01/14 17:47 did gyre and gimble:
Choosing a default linker seems like a system-integration issue rather
than something individual upstreams should be doing.
Yup, I'd rather keep things this way too if possible.
It can often catch integrators off-guard.
Hi,
On 01/20/2014 10:54 AM, Colin Guthrie wrote:
'Twas brillig, and Hans de Goede at 20/01/14 08:42 did gyre and gimble:
Hi,
For some reason after I've built the Xorg xserver from git, and then login
through gdm (on an otherwise unmodified F-20 install), the acls on
/dev/snd/pcm* (and likely
On Wed, Nov 20, 2013 at 10:54:15PM +0100, Lennart Poettering wrote:
On Tue, 19.11.13 02:33, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Mon, Nov 18, 2013 at 02:48:14PM +0100, Karel Zak wrote:
A few trivial patches... the duplications found by
On Tue, Jan 21, 2014 at 04:50:24PM +0100, Karel Zak wrote:
On Wed, Nov 20, 2013 at 10:54:15PM +0100, Lennart Poettering wrote:
On Tue, 19.11.13 02:33, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
wrote:
On Mon, Nov 18, 2013 at 02:48:14PM +0100, Karel Zak wrote:
A few trivial
This is a follow-up on this thread about directing the journal to a btrfs
subvolume, if it's desired to maintain one journal even when booting other
snapshots (such as doing a rollback):
http://lists.freedesktop.org/archives/systemd-devel/2014-January/016253.html
When I do this,
11 matches
Mail list logo
