IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
- add the values for objectGUID and whenChanged inside the ldb module,
so that the ldb module has only replicated attributes as input
metze
(This used to be commit 0ecb07e0526462529fb21cec30e789a9002b30a1)
w2k3 seems to do the same.
It's later useful, when we would have a large array
be could use a binary search
metze
(This used to be commit cd654f20e16c32f82ceb2b66453ce8d1be7020dd)
the merging of existing objects is not implemented yet...
there are a few ifdef REPLMD_FULL_ASYNC because we need to workarouns
ldb's async infrastructure (which don't handle full async sub requests nicely)
metze
(This used to be commit da4ff0e7ccde47b3e092313ba22422350cf50f78)
which prepares the replicated objects, the repl_meta_data ldb module
will then add the uSNCreated, uSNChanged and some other things and will apply
the objects to the partition specific ldb
metze
(This used to be commit 48d568a75b8109807af29f5d9604240c20c1a116)
- by default the operations goes to all partitions
- but some wellkown ones will go to just one partition
(DSDB_EXTENDED_REPLICATED_OBJECTS_OID for now)
I'll soon change the partitions module so that it'll attach a
DSDB_CONTROL_PARTITION_CONTEXT_OID control to give
the repl_meta_data or other partition specific modules a chance to
to know for which partition it should work.
metze
(This used to be commit 0ed53c6d0f4a4e43ff9c8943730eeb57c735201b)
when applying replicated objects.
the samldb module ignores such requests now...
and the repl_meta_data module has different functions
for the replicated and originating cases...
metze
(This used to be commit a4d5e0126cfd6135ab829f4984269e265a868a28)
But this is currently needed to make regpatch linking in
the dsdb/schema/schema_*.o object files.
the problem is that the linker doesn't find any references to public symbols
in this files and removes them from the link list.
gnu ld has a --whole-archive option, but it seems to be not portable...
I think the solution with prelinking using 'ld -r' to create one object file
for a subsystem instead of using 'ar -rcs' to create an archive for a subsystem...
jelmer: any ideas about this problem?
metze
(This used to be commit 46df7ff6e5e74eddcb81b5a195e82688d83afaf4)
- I'll add handling of replication meta data to it
for orginating changes
- I'll pass replication meta data via a ldb control
for applying replicated changes
- It will also update the replUpToDateVector attribute in
in root object of the partition
- It will handle deleted records by adding the isDeleted=TRUE attribute
and move them to the CN=Deleted Objects container of the partition
- I make a copy to play with the code without breaking
the LDAP backend setup
metze
(This used to be commit 045ddfe1ec626fab5e8fd75c5b47f0525b7ebb01)
Add a new module entrypoint to handle the new, interesting and
different mappings required for Fedora DS.
Andrew Bartlett
(This used to be commit 600c7f1a68c175b835ce45d13794a6f66bcc8493)
better handle the Samba3 backend.
I've refactored the password format patch to use the routines in
lib/samba3/smbpasswd.c, which has required me to move this into a
seperate subsystem, due to recursive dependencies.
Andrew Bartlett
(This used to be commit 14e2c877a82d1fcf060455f9b46de5767b71438d)
the ldb_to_drsuapi version need to be completed, but it's
currently not used...
metze
(This used to be commit 9b31e8c1f73aaf71522e33174c8c5415a95ac626)
using the following attribute syntaxes by default:
String(Numeric)
String(Printable)
String(Teletex)
String(IA5)
String(UTC-Time)
String(Case Sensitive)
Object(OR-Name)
Object(Access-Point)
Object(DN-String)
metze
(This used to be commit c10e1487708003d5a6c06b1547ce46ed4e4b0fe7)
