summaryrefslogtreecommitdiffstats
path: root/src/include
diff options
context:
space:
mode:
authorGreg Hudson <ghudson@mit.edu>2013-01-22 17:42:37 -0500
committerGreg Hudson <ghudson@mit.edu>2013-01-22 17:49:50 -0500
commit7665c0677b59574c2c7ccd016221f8f4beafd279 (patch)
treed1ec1717f811370bc9e0fdd0262ea7086dfd0055 /src/include
parent4b3937182b75e08eaf8f259828b018a2b6d2c111 (diff)
downloadkrb5-7665c0677b59574c2c7ccd016221f8f4beafd279.tar.gz
krb5-7665c0677b59574c2c7ccd016221f8f4beafd279.tar.xz
krb5-7665c0677b59574c2c7ccd016221f8f4beafd279.zip
Fix iprop log reinitialization
If the master iprop log is reinitialized to serial number 0, slaves will need to take a full dump--but after that happens, we need to know whether the slave has taken that full dump, we we don't offering full dumps indefinitely. So, record a timestamp in kdb_last_time when we reinitialize the log header, and compare the slave timestamp to kdb_last_time whenever it has the current serial number, even if it's 0. Test this by performing a propagation with sno 0 in t_iprop.py and detecting whether kpropd gets a second UPDATE_FULL_RESYNC_NEEDED response from kadmind. ticket: 7550 (new)
Diffstat (limited to 'src/include')
-rw-r--r--src/include/kdb_log.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/include/kdb_log.h b/src/include/kdb_log.h
index 14dbb2565..43d2fc41d 100644
--- a/src/include/kdb_log.h
+++ b/src/include/kdb_log.h
@@ -71,6 +71,7 @@ extern krb5_error_code ulog_map(krb5_context context,
const char *logname, uint32_t entries,
int caller,
char **db_args);
+extern void ulog_init_header(krb5_context context);
extern krb5_error_code ulog_add_update(krb5_context context,
kdb_incr_update_t *upd);
extern krb5_error_code ulog_delete_update(krb5_context context,