diff options
author | Matthieu Patou <mat@matws.net> | 2012-05-17 23:58:36 -0700 |
---|---|---|
committer | Matthieu Patou <mat@matws.net> | 2012-06-22 23:42:08 -0700 |
commit | c00485b25888b06a71a79d7c7cbf43f5445d33e0 (patch) | |
tree | 94f3523d659f0a09b5e8a0fea185aa63d2fee26e /docs-xml/manpages-3/tdbdump.8.xml | |
parent | 2f3adc001eba8027fb7ae46e2c0fa7342c166d1a (diff) | |
download | samba-c00485b25888b06a71a79d7c7cbf43f5445d33e0.tar.gz samba-c00485b25888b06a71a79d7c7cbf43f5445d33e0.tar.bz2 samba-c00485b25888b06a71a79d7c7cbf43f5445d33e0.zip |
s4-dsdb: operational handle modifyTimeStamp on the CN=aggregate DN
modifyTimeStamp is a generated attribute, for most object it's generated
directly from the whenChanged attribute. But for the CN=aggregate object
in the schema we have to handle it in a different way, that's because
for this object whenChanged!=modifyTimeStamp (as checked against Windows
2003R2 DCs) instead the modifyTimeStamp reflect the timestamp of the
most recently modified and loaded schema object (that is to the one with
the highest USN before the schema was reload due to timeout or by the
reloadSchemaNow command).
Some third party are using this information to know if they have to
update their schema cache and also to check that schema updates have
been correctly reloaded by the DC, a good example of this behavior is
exchange 2010.
Diffstat (limited to 'docs-xml/manpages-3/tdbdump.8.xml')
0 files changed, 0 insertions, 0 deletions