Bug#584434: Bug#588536: krb5-kdc: Should it start before gdm/kdm/etc and after DNS servers?
What happens in the case where LDAP is hanging and an administrator is
trying to log in as root or some other user not authenticated by krb5?
It sounds like krb5-kdc not being started before kdm can be solved by
waiting. Having graphical logins on a KDC for a traditional Kerberos
realm is not a very common operation; I understand that it may be more
common in debian-edu, although I'd think even there not hugely common.
If my understanding that blocking kdm on krb5-kdc could delay/prevent
administrative logins in a case where something is hanging trying to
come up, then I'm against making this change or encouraging display
managers to do so.
If waiting for krb5-kdc to come up is not sufficient to unblock kdm,
then there's some other deeper bug here and that problem is fixed.
If my understanding is inaccurate, I would be happy to evaluate the
change based on the new understanding.
Reply to: