From ab83005b30c621230db674faa1d123f44c9122e7 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Wed, 11 Apr 2012 16:02:44 +0200 Subject: s3:registry: update the seqnum in the subkey cache at the end of regval_store_keys The purpose is to prevent next reads from going to disk. Note that this will currently only be effective with local tdbs, not with ctdb: For tdb, store and delete bump the seqnum while transaction commit does not. For ctdb, transaction commit bumps the seqnum, while store and delete don't... This needs fixing (in ctdb). Signed-off-by: Andreas Schneider --- source3/registry/reg_backend_db.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'source3/registry') diff --git a/source3/registry/reg_backend_db.c b/source3/registry/reg_backend_db.c index d4f52b7571..65355aec23 100644 --- a/source3/registry/reg_backend_db.c +++ b/source3/registry/reg_backend_db.c @@ -1260,7 +1260,11 @@ static NTSTATUS regdb_store_keys_action(struct db_context *db, W_ERROR_NOT_OK_GOTO_DONE(werr); } - werr = WERR_OK; + /* + * Update the seqnum in the container to possibly + * prevent next read from going to disk + */ + werr = regsubkey_ctr_set_seqnum(store_ctx->ctr, dbwrap_get_seqnum(db)); done: talloc_free(mem_ctx); -- cgit