[PATCH] New external idmap module
Volker.Lendecke at SerNet.DE
Wed May 31 08:21:33 GMT 2006
On Tue, May 30, 2006 at 04:46:24PM -0700, Dave Daugherty wrote:
> usable in the presence of our proprietary shared object library - the
> rule of thumb being that the proprietary shared object library stands
> alone, and is useful even if Samba is not around.
This is ok if the proprietary library is shipped with every
copy of the operating system. Otherwise we could not link
against the HP-UX libc for example.
> It doesn't matter though: I just want to do the right thing. I
> originally was going to do a Unix sockets interface too, but got shot
> down as too complicated. But if everyone agrees that Simo's Unix socket
> interface or that Michael's scripting approach is what is required for
> compliance then I am happy with either.
For compliance this is the right way, yes.
> But I still need to control the use of winbind_idmap.tdb. This I can
> also do external to the main source tree and publish my changes on our
> web site, but wouldn't it be nice if we all could use the same code in
> the main branch.
Why do you need to change existing mappings? If doing this
you also need a process that walks the whole file system and
changes owners and acls. If you have this, this process can
easily blow away winbindd_idmap.tdb.
-------------- 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/ac9d822a/attachment.bin
More information about the samba-technical