Restrictions on invocationID?

[Stefan (metze) Metzmacher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan (metze) Metzmacher schrieb:
> Andrew Bartlett schrieb:
>> Metze:
> 
>> I'm trying to implement the cn=configuration container against LDAP.
>> Currently, it doesn't work because we fix the invocationID *and*
>> objectGUID of the cn=NTDS Settings,cn=$COMPUTER... record to be a
>> 'fixed' random value (ie, not generated by the LDAP backend).  
> 
>> OpenLDAP objects to us setting it's entryUUID values.  My questions is:
>> does the invocationID need to match the objectGUID on that entry?
> 
> Hi Andrew,
> 
> in the "load schema by default" patch I changed our way to handle this.

Here is the patch again as it was to large for samba-technical in my
first mail...

metze
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGNJEAm70gjA5TCD8RAq1bAKCytUyvWtRu04/cVUZ+CD7EFiYT1QCgrMIE
rfc2YyMEiqFXMcu7VQi72dM=
=+OV3
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: schema-loading-12.diff.gz
Type: application/x-gzip
Size: 22451 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20070429/011b9527/schema-loading-12.diff.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: schema-loading-12.diff.gz.sig
Type: application/pgp-signature
Size: 65 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20070429/011b9527/schema-loading-12.diff.gz.bin