WINBINDD_SOCKET_DIR hardcoded

[Volker Lendecke]

On Thu, Oct 12, 2006 at 06:25:09PM +0400, Dmitry Butskoy wrote:
> We had a task to cause a fileserver to work in two different domains 
> simultaneously. (Such a task was needed for gradual switching of clients 
> from the one domain to another, without global system's stopping etc.)
> 
> Such a task requires two instances of Samba. One uses normal 
> config/lib/cache pathes, other uses an alternate.
> 
> Samba has a good possibility to differ config file's path (-s option), 
> log file dir (-l), lock and pid directories ("lock directory", "pid 
> directory" in the config file). But one thing has remained unhandled -- 
> it is now hardcoded WINBINDD_SOCKET_DIR path.

Hardcoding that is deliberate. If you do a 

getent passwd <username>

which winbind should that command connect to? Winbind _is_
a global resource, the migration scenario you are describing
is correctly handled with Windows trust relationships.

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20061012/246e8e22/attachment.bin