From 7665c0677b59574c2c7ccd016221f8f4beafd279 Mon Sep 17 00:00:00 2001 From: Greg Hudson Date: Tue, 22 Jan 2013 17:42:37 -0500 Subject: 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) --- src/include/kdb_log.h | 1 + 1 file changed, 1 insertion(+) (limited to 'src/include') diff --git a/src/include/kdb_log.h b/src/include/kdb_log.h index 14dbb25659..43d2fc41dd 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, -- cgit