s3:registry: implement values_need_update and subkeys_need_update in the smbconf...

It simply calls to the regdb functions.
This fixes a caching issue uncovered by recent changes.

Autobuild-User: Michael Adam <obnox@samba.org>
Autobuild-Date: Sat May  5 04:10:43 CEST 2012 on sn-devel-104

diff --git a/source3/registry/reg_backend_smbconf.c b/source3/registry/reg_backend_smbconf.c
index 11abb9cc6660e747b425eeadfa58c54fa104ed0c..a056654c8948e1510903dc974c044a01a39b333a 100644 (file)
--- a/source3/registry/reg_backend_smbconf.c
+++ b/source3/registry/reg_backend_smbconf.c
@@ -81,6 +81,15 @@ static WERROR smbconf_set_secdesc(const char *key,
        return regdb_ops.set_secdesc(key, secdesc);
 }
 
+static bool smbconf_subkeys_need_update(struct regsubkey_ctr *subkeys)
+{
+       return regdb_ops.subkeys_need_update(subkeys);
+}
+
+static bool smbconf_values_need_update(struct regval_ctr *values)
+{
+       return regdb_ops.values_need_update(values);
+}
 
 /*
  * Table of function pointers for accessing smb.conf data
@@ -96,4 +105,6 @@ struct registry_ops smbconf_reg_ops = {
        .reg_access_check = smbconf_reg_access_check,
        .get_secdesc = smbconf_get_secdesc,
        .set_secdesc = smbconf_set_secdesc,
+       .subkeys_need_update = smbconf_subkeys_need_update,
+       .values_need_update = smbconf_values_need_update,
 };