summaryrefslogtreecommitdiff
path: root/WHATSNEW4.txt
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2009-09-15 14:06:07 -0700
committerAndrew Tridgell <tridge@samba.org>2009-09-15 14:52:23 -0700
commitbfd0877261883d1d6ef1d1757dad386332a8db37 (patch)
treed62e4fc241b4281c52b7d49bea05f6f8972928b2 /WHATSNEW4.txt
parentf5aec9ebb4bf5d0e6f8c6974a485bc5cd2899fdd (diff)
downloadsamba-bfd0877261883d1d6ef1d1757dad386332a8db37.tar.gz
samba-bfd0877261883d1d6ef1d1757dad386332a8db37.tar.bz2
samba-bfd0877261883d1d6ef1d1757dad386332a8db37.zip
s4-repl: don't do double replication
When we replicate from a remote DC, we need to note the new uSN that the local changes have resulted in, and modify the uSN that the notify task uses to determine if it should send a ReplicaSync message back to the remote DC. Otherwise we end up always triggering a ReplicaSync every time we replicate from another DC
Diffstat (limited to 'WHATSNEW4.txt')
0 files changed, 0 insertions, 0 deletions