[krbdev.mit.edu #6338] Debian Bug #511348: cpu spins when ldap not available

[Sam Hartman via RT]

Please take a look at http://bugs.debian.org/511348 It seems like
krb5_db_inited is kind of confused.  Some of the code (libkadm5)
treats it as a boolean function; some code (kdb keytab) treats it as
returning an error code.  For unexplained reasons, krb524d spins
sometimes against an ldap backend.

I'm not sure entirely what's going on here, but I suspect that the
policy db and the principal db are getting out of sync or something.
I understand we're dropping krb524d from the release, but it seems like some issues may still result from this.

--Sam