issue with temp policy lock file and kdb5_util error

[Will Fiveash]

Recently someone was having issues with kprop working and the problem
appears to be related kpropd aborting when processing a resync with the
master KDC and leaving temp principal files behind like:

loki# ls princ*
principal.ulog         principal~.kadm5       principal~.ok
principal~             principal~.kadm5.lock

My question: is there an existing command that an admin can run that
will clean this up so they can retry the kprop resync?  If not, it seems
like there should be.

-- 
Will Fiveash
Oracle
http://opensolaris.org/os/project/kerberos/
Sent using mutt, a sweet text based e-mail app: http://www.mutt.org/