trustdom_cache when winbind is running?

Volker Lendecke Volker.Lendecke at SerNet.DE
Fri Jun 3 12:53:35 GMT 2005


Following setup: Samba as a domain member in a HA cluster, multiple instances
running separated with 'pid directory', 'lock directory', 'interfaces' and so
on running fine. This is done so that services can be moved around happily by
just restarting the smbd/nmbd pair somewhere else.

Winbind with its own smb.conf and its own 'lock directory'. The domain we're
member of trusts another domain, winbind writes the info into its own trusted
domain cache, gencache.tdb.

Trusted user connects to a smbd, this smbd does not find the trustdom entry in
its private gencache.tdb. Thus it maps the user to its own domain -> bang...

Wouldn't a WINBIND_IS_TRUSTED_DOMAIN query be much smarter for this case?
winbind would not need to bother with gencache.tdb, as it has a list of
domains in memory anyway. So the trustdom_cache would only be used in the
non-winbind case. And to be honest, this is broken anyway IMHO.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :

More information about the samba-technical mailing list