Behaviour of repsTo last_success and last_attempt

[Void]

Hi,

I finally got to get together a patch for repsTo times. With this
patch, repsTo wont be set to 0 repeatedly, and now shows correct
times.

In short this patch removes DRSUpdateRefs from every replication
cycle, and depends on getncchanges updating repsTo accordingly. Also
DsReplicaSync will not only be called for real changes, but also every
hour, which seems to be what MS-ADTS suggests.

Next will be ReplUptoDateVector, because this is what Windows tools
ask for, to determine if a replication is up to date. There are also
some problems in setting the times correctly.

As always, please comment, criticize and give any tips ;)

Thanks,
Dirk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Behaviour-of-repsTo-last_success-and-last_attempt-te.patch
Type: text/x-patch
Size: 6826 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160627/cb4024cd/0001-Behaviour-of-repsTo-last_success-and-last_attempt-te.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Behaviour-of-repsTo-last_success-and-last_attempt.patch
Type: text/x-patch
Size: 3403 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160627/cb4024cd/0002-Behaviour-of-repsTo-last_success-and-last_attempt.bin>