On 25.10.2015 09:41, poma wrote:
>
> Hi Fi
>
> tty0: Failed to start Login Service - intermittently
> produces overall delays and timeouts.
>
> systemd 227
...
Logind does not break w/ systemd.log_level=debug
of course.
___
systemd-devel mailing lis
I have a question: the support of mdm display manager in Systemd is not good
,all right?
SAM
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi Fi
tty0: Failed to start Login Service - intermittently
produces overall delays and timeouts.
systemd 227
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
# journalctl systemd-logind
..
[ 22.458993
Hi Tobias,
> Most non-trivial docker images need that. Should I open a feature request
that makes sense. I asked the same some time ago. It's on their
TODO-list, but at that time they didn't use Github for their feature
requests. See https://github.com/systemd/systemd/blob/master/TODO#L60.
Please
Am 25.10.2015 00:41 schrieb "Zbigniew Jędrzejewski-Szmek" :
> There is not built-in support for that.
>
> You can always look at /proc/1/environ from privileged processes, or add
> a generator script to create the units you need from that file.
Most non-trivial docker images need that. Should I op