[PATCH] New external idmap module
Volker.Lendecke at SerNet.DE
Wed May 31 09:08:31 GMT 2006
On Wed, May 31, 2006 at 09:36:05AM +0100, Gautier, B (Bob) wrote:
> Not fine by me!
Ok. I would be fine adding a negative cache to the id map.
What I still fail to see is a valid reason to change
existing mappings. Could you please be a bit more specific
why you need to change an existing mapping in a situation
that does not allow you to remove winbindd_idmap.tdb and
> FWIW I would love to see a mechanism that would allow all the idmap
> functionality to be segregated into a separate process, independent of
> the mainline Samba code, so that 1) we have complete control over the
> idmap algorithm and 2) we can use a custom algorithm whilst still using
> a standard, out-of-the-distro-vendors-box, build of Samba for which we
> can get support.
Both of these features I think are provided by the script
solution. What is it specifically that this script solution
does not give you?
> Although I have not followed the discussion in every detail, I think
> that means I am in support of the original external idmap module
> proposal, complete with TCP socket support (because I think if it's not
> in the basic module, someone will write a proxy eventually anyway).
> Isn't an external, TCP-reachable idmap module relevant to the Samba
> clustering work? I wonder if their messaging protocols are worth using
> here, at least.
It is, but I do not expect clusters to change existing
mappings on an ongoing basis, so for this application I
would very much assume that the script solution would be
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20060531/2bccfe6f/attachment.bin
More information about the samba-technical