Further:
Dec 19 18:47:48 fedora16 dbus[1097]: [system] Activating via systemd:
service name='org.freedesktop.login1'
unit='dbus-org.freedesktop.loginervice'
Dec 19 18:47:48 fedora16 dbus-daemon[1097]: dbus[1097]: [system] Activating
via systemd: service name='org.freedesktop.login1'
unit='dbus-orreedesktop.login1.service'
Dec 19 18:47:48 fedora16 systemd-logind[1203]: Failed to open
/sys/class/tty/tty0/active: No such file or directory
Dec 19 18:47:48 fedora16 systemd-logind[1203]: Failed to fully start up
daemon: No such file or directory
Dec 19 18:47:48 fedora16 systemd[1]: systemd-logind.service: main process
exited, code=exited, status=1
Dec 19 18:47:49 fedora16 systemd[1]: Unit systemd-logind.service entered
failed state.
I'm trying to track things further. I'll let you know how I get on.
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