samba.git/source4, branch talloc-2.0.0 Unnamed repository; edit this file 'description' to name the repository. First attempt to implement dcesrv_drsuapi_DsGetNCChanges 2009-09-03T09:10:49+00:00 Anatoliy Atanasov anatoliy.atanasov@postpath.com 2009-09-02T14:39:28+00:00 38995d7cbb0c3143eb1fea0215863321349c7bbe So far it returns the ctr6 responce without proper linked attributes support and metadata. A couple of improvements are the filter in the search uses '(uSNChanged>=N)', added extended dn search support, non-replicated attributes are excluded from the result. 
So far it returns the ctr6 responce without proper linked attributes
support and metadata. A couple of improvements are the filter in the search
uses '(uSNChanged>=N)', added extended dn search support, non-replicated attributes
are excluded from the result.
Fix the dsdb_syntax_OID_ldb_to_drsuapi function 2009-09-03T09:10:42+00:00 Anatoliy Atanasov anatoliy.atanasov@postpath.com 2009-09-02T14:20:16+00:00 957a9285c22c5f4412154bd84a82d66fe759b0f5 This replace the dsdb_syntax_FOOBAR_ldb_to_drsuapi function, which was left as a TODO code. Implementation in both added functions is completely identical and probably should differ in the future. 
This replace the dsdb_syntax_FOOBAR_ldb_to_drsuapi function,
which was left as a TODO code. Implementation in both added functions
is completely identical and probably should differ in the future.
another large change to the linked_attribute module 2009-09-03T08:36:10+00:00 Andrew Tridgell tridge@samba.org 2009-09-03T08:36:02+00:00 d3d6713c599fa74f5fdd890bd00ab0dd721749d8 This one copes with deleted objects where linked attributes have been set on the module. We hit this when we do the ldb wipe at the start of a provision, which trigers linked attribute updates, but for objects that have disappeared. We need to ensure that the linked attribute updates only happen on the right object, and if the object gets re-created (as happens with a provision) then it is not the right object. To cope with this we record the GUID of the object when the operation that triggered the linked attribute update comes in, and then find the DN by suing that GUID when we apply the change in the prepare commit hook. 
This one copes with deleted objects where linked attributes have been
set on the module. We hit this when we do the ldb wipe at the start of
a provision, which trigers linked attribute updates, but for objects
that have disappeared. We need to ensure that the linked attribute
updates only happen on the right object, and if the object gets
re-created (as happens with a provision) then it is not the right
object.

To cope with this we record the GUID of the object when the operation
that triggered the linked attribute update comes in, and then find the
DN by suing that GUID when we apply the change in the prepare commit
hook.
hook on prepare_commit instead of transaction_end 2009-09-03T08:36:10+00:00 Andrew Tridgell tridge@samba.org 2009-09-03T08:33:17+00:00 b72b8f6e7d6a83999153b71edd6f50a1803eff95 This allows for safe transaction end aborts 
This allows for safe transaction end aborts
greatly simplify the transaction processing in the partition module 2009-09-03T08:36:09+00:00 Andrew Tridgell tridge@samba.org 2009-09-03T08:32:42+00:00 47f52e7a337f1f0e35c77f480146bbee3ac1d309 Now that ldb is calling prepare commit separately, the job of the partition module on transaction end is much simpler (and more robust!) 
Now that ldb is calling prepare commit separately, the job of the
partition module on transaction end is much simpler (and more robust!)
show more reasonable object counts during a vampire 2009-09-03T08:36:09+00:00 Andrew Tridgell tridge@samba.org 2009-09-03T08:31:45+00:00 7dbe0797b1c98fc63af20af03c2b36cc04a7386e We now show the total number of objects we have processed, which gives the user a better idea of how much has been done. A vampire on a large domain can take an hour or more (which needs to be fixed btw, it is a problem with the lack of scalability of the ltdb index code). Watching the same msg for an hour makes you wonder if any progress is being made! 
We now show the total number of objects we have processed, which gives
the user a better idea of how much has been done. A vampire on a large
domain can take an hour or more (which needs to be fixed btw, it is a
problem with the lack of scalability of the ltdb index code). Watching
the same msg for an hour makes you wonder if any progress is being
made!
always use prepare_commit in ldb transaction commits if possible 2009-09-03T08:36:09+00:00 Andrew Tridgell tridge@samba.org 2009-09-03T08:29:58+00:00 bfccc4590dc94b37258b7225d153c4c01d1a28d6 The reason we need this is to make multi-tdb transactions safe, with the partition module. The linked_attributes and repl_meta_data modules now do extra processing when the transaction ends, and that processing can fail. When it fails we need to cancel the transaction, which we can only do if the hook is on the prepare commit instead of the end transaction call. Otherwise the partition module cannot ensure that no commit has been done on another partition. 
The reason we need this is to make multi-tdb transactions safe, with
the partition module. The linked_attributes and repl_meta_data modules
now do extra processing when the transaction ends, and that processing
can fail. When it fails we need to cancel the transaction, which we
can only do if the hook is on the prepare commit instead of the end
transaction call. Otherwise the partition module cannot ensure that no
commit has been done on another partition.
added dsdb_find_guid_by_dn() 2009-09-03T08:36:09+00:00 Andrew Tridgell tridge@samba.org 2009-09-03T08:27:29+00:00 c37f290043c55ec6428a313b4ec3ca2f91e5e98e This will be used by the linked_attribute module 
This will be used by the linked_attribute module
allow setting of the debug level in python from C 2009-09-03T08:36:09+00:00 Andrew Tridgell tridge@samba.org 2009-09-03T03:03:31+00:00 617bbd913dcd6335cfcee3db6d23e8d3262dd566 






change repl_meta_data to process linked_attributes structures in end_transaction
2009-09-03T08:36:09+00:00

Andrew Tridgell
tridge@samba.org

2009-09-03T02:55:57+00:00

348824da759a78b06e75d6ab7f8f85aa9912957c

When running at functional level 2 or above, the repl_meta_data module
can receive linked attribute structures from the repl replication
task. These attributes can come through DRS before the associated
objects have been created. To cope with this, we need to process
linked attributes in the end_transaction hook.





When running at functional level 2 or above, the repl_meta_data module
can receive linked attribute structures from the repl replication
task. These attributes can come through DRS before the associated
objects have been created. To cope with this, we need to process
linked attributes in the end_transaction hook.