[cifs-protocol] RID Allocation behaviour

[Andrew Bartlett]

G'day

Tridge and I are working on Samba4's implementation of the distributed
RID allocation. 

We are unclear on a number of aspects of the expected behaviour,
particularly when the RID manager is not the DC adding users.

I'll describe this in terms of the 'RID manager DC' and the 'remote DC'

For example:

It appears that the Remote DC is responsible for updating the ridNextRID
attribute, but rather than storing the next RID, it appears to store the
last allocated RID.  The actual remote DC allocation process for RIDs
appears undocumented.

It appears the RID Manager DC is responsible for updating the
rIDAllocationPool for each DC, and the rIDAvailablePool.  We think the
remote DC is responsible for ridPreviousAllocationPool and allocates
RIDs from that pool, but this is only described in the schema doc.  

Any light you can shed on this process would be most appreciated.

Thanks,

Andrew Bartlett
-- 
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Cisco Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20100106/3210e6ef/attachment.pgp>