Problem also occurs in openSUSE:
http://lists.opensuse.org/opensuse-bugs/2011-12/msg00945.html
"There is no tty0 on zLinux, only the console device:"
Patch from the systemd-devel list:
diff --git a/src/logind.c b/src/logind.c
index 4633a5e..f491cee 100644
--- a/src/logind.c
+++ b/src/logind.c
@@ -906,6 +906,8 @@ static int manager_connect_console(Manager *m) {
m->console_active_fd = open("/sys/class/tty/tty0/active",
O_RDONLY|O_NOCTTY|O_CLOEXEC);
if (m->console_active_fd < 0) {
+ if (errno == ENOENT)
+ return 0;
log_error("Failed to open /sys/class/tty/tty0/active: %m");
return -errno;
}
--
On 12/22/11 3:48 AM, "Dan Horák" <dan(a)danny.cz> wrote:
Neale Ferguson píše v St 21. 12. 2011 v 11:49 -0600:
Hi,
I see in the
release notes a reference to a delay when logging on (or
su¹ing). I assume
you know the cause, in case an strace shows a timeout when
polling on some
dbus communication:
thanks for the info, I suspect that systemd doesn't start
something or
it fails or something like that. It's definitely something I'll
look at.
Dan
_______________________________________________
s390x mailing
list
s390x(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/lis
tinfo/s390x