From 6f3a8b41f5b43c35263a401b2bddbe4e49812b85 Mon Sep 17 00:00:00 2001 From: Matthieu Patou Date: Wed, 30 May 2012 10:43:27 -0700 Subject: s4-dsdb: Add/Update SCHEMA_SEQ_NUM key in the metadata.tdb after schemaUpdateNow The idea is to signal to other process accessing the database that the schema was forced to be reloaded and so they should reload as well. --- source4/dsdb/samdb/ldb_modules/schema_load.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'source4/dsdb/samdb/ldb_modules/schema_load.c') diff --git a/source4/dsdb/samdb/ldb_modules/schema_load.c b/source4/dsdb/samdb/ldb_modules/schema_load.c index f922aabba9..9ae99a44b2 100644 --- a/source4/dsdb/samdb/ldb_modules/schema_load.c +++ b/source4/dsdb/samdb/ldb_modules/schema_load.c @@ -363,8 +363,8 @@ static int schema_load_extended(struct ldb_module *module, struct ldb_request *r *lastts = 0; ldb_set_opaque(ldb, DSDB_OPAQUE_LAST_SCHEMA_UPDATE_MSG_OPAQUE_NAME, lastts); - /* This is a no-op. We reload as soon as we can */ - return ldb_module_done(req, NULL, NULL, LDB_SUCCESS); + /* Pass to next module, the partition one should finish the chain */ + return ldb_next_request(module, req); } -- cgit