[krbdev.mit.edu #6875] kdb5_util mkey operations hit assertion when iprop is enabled

[Greg Hudson via RT]

At a surface level, the bug is that in the current design, ulog_map() 
must be invoked by callers of kdb_put_principal(), and the kdb5_util mkey 
commands don't do that.

I am concerned about this comment in the ulog_map() call from kdb5_util 
load: "We don't want to take out the ulog out from underneath kadmind so 
we reinit the header log."  Are there iprop log contention issues with 
modifying the KDB from multiple processes at once?  (If so, we have a 
problem with kadmin.local.)  I need to check in with Ken on this.