diff options
| author | Matthieu Patou <mat@matws.net> | 2012-05-09 22:08:55 -0700 |
|---|---|---|
| committer | Matthieu Patou <mat@matws.net> | 2012-06-22 23:16:04 -0700 |
| commit | 1521bb95a7bb3df5cb3a128085a088cb09555f8b (patch) | |
| tree | a2a28b508601ccf25078b215c519950a72319287 /source3/modules/vfs_extd_audit.c | |
| parent | f8fd615c5950bab9a38cd31872ae447ffdc974f3 (diff) | |
| download | samba-1521bb95a7bb3df5cb3a128085a088cb09555f8b.tar.gz samba-1521bb95a7bb3df5cb3a128085a088cb09555f8b.tar.bz2 samba-1521bb95a7bb3df5cb3a128085a088cb09555f8b.zip | |
dsdb-schema: do not reload more often than schema_reload_interval
Samba 4 use to try to reload the schema every time dsdb_get_schema was
called (which could be 20+ time per ldb request). Now we only reload at
most every xx seconds (xx being the value of dsdb:"schema_reload_interval"
or 120). The timestamp of the last reloaded schema is kept in the
dsdb_schema object. There is also a timestamp in the ldb_context, that
is used by the LDAP server to know if it has to reload the schema after
handling the request. This is used to allow that the schema will be
immediately reload after a schemaUpdateNow request has been issued, the
reload can't occur in the handling of the LDAP request itself because
we have a transaction autostarted.
Diffstat (limited to 'source3/modules/vfs_extd_audit.c')
0 files changed, 0 insertions, 0 deletions