[PATCH] rid allocator in passdb backend

Hi! This patch puts a RID allocator into the passdb backend. The outside interface are two calls. pdb_max_used_rid is for net rpc vampire to set the maximum RID that the PDC gave us. pdb_allocate_rid_for_gid allocates a new RID for the given unix group id. The passdb backend must allocate RIDs f

Re: [PATCH] rid allocator in passdb backend

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > It would be nice to update the samba.schema only once, so we should > now also add the account policy values, etc ... to sambaDomainInfo > (all stuff we'll later use for the SAM system) Also add sambaGroup > now, would be nice.(with the stuff we'll l

Re: [PATCH] rid allocator in passdb backend

At 20:26 17.10.2002 +0200, [EMAIL PROTECTED] wrote: Hi! This patch puts a RID allocator into the passdb backend. The outside interface are two calls. pdb_max_used_rid is for net rpc vampire to set the maximum RID that the PDC gave us. pdb_allocate_rid_for_gid allocates a new RID for the give

Re: [PATCH] rid allocator in passdb backend

At 09:42 18.10.2002 +0200, [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > It would be nice to update the samba.schema only once, so we should > now also add the account policy values, etc ... to sambaDomainInfo > (all stuff we'll later use for the SAM system) Also add sa

Re: [PATCH] rid allocator in passdb backend

> This patch does not yet handle the case where we already have a > sambaDomainInfo entry, but no rid attribute. I do not know how you can > make sure that you do not end up with to rid attributes. Does anybody > know how to do this? Define the rid attribute to be SINGLE-VALUE in the schema. Ma

Re: [PATCH] rid allocator in passdb backend

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi again! > This patch puts a RID allocator into the passdb backend. The outside interface > are two calls. I forgot one thing: This patch does not yet handle the case where we already have a sambaDomainInfo entry, but no rid attribute. I do not kno