[krbdev.mit.edu #7784] krb5-1.12 beta2 - kpropd ulog_replay failed error

[Greg Hudson via RT]

That error comes from kdb5.c line 428, which happens if 
krb5int_get_plugin_dir_data succeeds but returns an empty list.  If the 
plugin functions had encountered an EINTR (which I don't think is even 
possible with opendir/readdir/dlopen), then a different error would be 
generated--either "Unable to find requested database type" or "plugin 
symbol 'kdb_function_table' lookup failed".  So, I don't really like the 
SIGUSR1 theory.  I don't have another theory, though.

Also of note: that code path is only executed for the first KDB function 
for a context.  After that the DB2 vtable is picked out of the cache by 
kdb_find_library().