]> git.ipfire.org Git - thirdparty/krb5.git/commit
Remove ulog_check(); the ulog is not a DB journal
authorNicolas Williams <nico@cryptonector.com>
Thu, 25 Oct 2012 23:26:10 +0000 (18:26 -0500)
committerGreg Hudson <ghudson@mit.edu>
Wed, 23 Jan 2013 19:46:06 +0000 (14:46 -0500)
commitceac9a66ce2ae844b16ec318934004439f5b3ae5
tree0324ff1f0eb2bb695e00f9db2964415d1b9879ca
parent720e0f5bcf481db3b6e43652cb6577c012b5337e
Remove ulog_check(); the ulog is not a DB journal

The db2 DB is not power-fail safe.  There's no point trying to
replay an incompletely committed entry from the ulog at kadmind
startup time.  For that matter, even if the db2 DB was power-fail
safe there'd be no point replaying an uncommitted entry from the
ulog as the libkadm5srv app (nor any client of it, as in the case of
kadmind) will not have received any notice of success -- it'd be
wrong to complete that operation later when the user thought it'd
failed.

[ghudson@mit.edu: merge with master, adjust comment]

ticket: 7552 (new)
src/lib/kdb/kdb_log.c