On Tue, 2008-05-27 at 18:43 -0700, Howard Chu wrote:
Andrew Bartlett wrote:
> On Tue, 2008-05-27 at 18:22 -0700, Howard Chu wrote:
>>> This needs to occur even between databases on the server, but I won't=
>>> it occur outside the known trees.
>> It's already possible for operations in one database to reference entr=
ies in a
>> different database, so that aspect of validation should be
>> noted before, "validation" is generally bogus to
begin with. In partic=
>> how do you create entries with circular references? If you
>> to nonexistent entries, you can't set the references
until after all o=
>> entries have been created. This means that you cannot backup
>> has these references and then later reload it in a single
> An interesting point, but I need to match the windows runtime
Only when it has a visible impact on other clients. What software will br=
if the directory allows you to add new entries that contain
references? What will break if the directory allows you to modify a refer=
attribute to point to a nonexistent entry?
Sure, I'm not asking for a change to default behaviours. I'm listing
the things that our testsuite finds are differences, and looking for
There's a lot of Windows behavior that is clearly wrong, by any
metrics. You need to be a bit more selective in prioritizing the list
things to chase down.
This is the currently the top priority for an LDAP Backend for Samba4. =20
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc.
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----