prefix_map module add operation fails to modify schema

Andrew Bartlett abartlet at
Tue Jul 1 09:32:06 GMT 2008

On Tue, 2008-07-01 at 12:19 +0300, Anatoliy Atanasov wrote:
> Hi metze,
> The approach we have implemented aims to emulate Windows behavior, where the Schema cache is updated after modification upon receipt of a schemaUpdateNow request. Initially we intended to implement a much simpler solution, but at SambaXP after some discussion with abartlet decided that
> Windows behavior should be incorporated in samba. 
> If we do not support the schemaUpdateNow request, a lot of DEA will not be able to be installed. 
> I agree that we can go with your implementation and it's much simpler than what I've done. If there are no other comments I'll implement it right away.

What is the conflict here?

To support existing clients, just ensure you don't error on
schemaUpdateNow.  All that needs to happen is to have updated the schema
by the time that returns - it will happen on a timer anyway, so if it
happen to already have occurred (because it is actually done real-time)
what is the harm?

schemaUpdateNow should be used to trigger all the other users of the
schema to reload. (Possibly easier if the LDAP server remains a single

Andrew Bartlett

Andrew Bartlett
Authentication Developer, Samba Team 
Samba Developer, Red Hat Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :

More information about the samba-technical mailing list