[Sam Hartman] > My understanding is that if we make the change you are proposing, > then kdm will not start until after the KDC starts.
To be exact, kdm will not start until after the krb5-kdc init.d script exits. > We previously made the KDC start after LDAP. > > My concern is that I want a local administrative user to be able to use > kdm to log in if > 1) the kdc fails to start > 2) the kdc or LDAP hangs starting--that is, the init script never > exits. > > I'm trying to evaluate how your change affects that. Your answers > are brief to the point that they do not clarify my understanding. If a init.d script hangs, the boot will not succeed (doh :), and the no login prompt are likely to show up. But if a script hangs, the display managers are likely to block access anyway because the nologin flag is still present. If you try to order the boot scripts to ensure admin access even when boot scripts hang, I believe you will are trying to solve an impossible task. If krb5-kdc hangs during boot, the admin should boot into runlevel 1 to fix the problem and reboot to start both kdm and a now non-hanging krb5-kdc. What was the ordering of kdm and krb5-kdc with the legacy boot sequencing? Is the same ordering kept with the dependency boot sequencing? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
