s3:registry: update the seqnum in the subkey cache at the end of regval_store_keys
commitab83005b30c621230db674faa1d123f44c9122e7
authorMichael Adam <obnox@samba.org>
Wed, 11 Apr 2012 14:02:44 +0000 (11 16:02 +0200)
committerAndreas Schneider <asn@samba.org>
Wed, 25 Apr 2012 12:31:11 +0000 (25 14:31 +0200)
treee4fa60680ec07d812467d5dd3995b0ab7a772d45
parent4367071f62d2994f1d3d4f33d45fcd6b4c7bec26
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 <asn@samba.org>
source3/registry/reg_backend_db.c