Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
RT-Send-CC:
X-RT-Original-Encoding: iso-8859-1
Content-Length: 929

Sending to krb5-bugs is sufficient; you do not need to forward to krb5-
bugs and krbdev.

I do not really understand how kdb5_util could exit with status 2 
(implying that it got all the way through load_db(), since nothing in 
the code calls exit(2)) but not reset the ulog header with the code in 
your earlier patch from issue #7588.  Also, I would really love to know 
in what way kdb5_util load is sometimes failing, since that should be 
rare.  Unfortunately, kdb5_util was written as a command-line tool and 
not a component of a server, so when it fails, it just writes to stderr 
instead of logging.

Rather than add a redundant second piece of code to reinitialize the 
ulog header on failure, I wonder if we should make load_db() leave the 
ulog header alone until after it has called krb5_db_promote().  I don't 
see any point in having a window where the ulog header doesn't reflect 
the status of the live database.