> Why don't you use 2 different Linux boxes each one acting as a domain
> controller?
In fact, the box is a domain member, not a domain controller (that's why I
use winbind, for fetching accounts and allowing access to the box shares).
Anyway, I found a workaround, pretty nasty though: as I am migrating from
one domain to another, and the situation is temporary, I pasted the results
from one winbind (with wbinfo) in /etc/passwd and /etc/group, shut down this
winbind, started the other one, and, in combination, I have accounts from
both domains up and running (as seen by 'getent passwd' and 'getent group').
And when migration is done, I'll delete the added entries and rely on
winbind. Anyway, I think it would be great if there were a way to make
nsswitch.conf work with more than one winbind simultaneously...
Yours,
Fernando del Valle
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Fernando del Valle
> Sent: 25 iunie 2003 19:22
> To: [EMAIL PROTECTED]
> Subject: [Samba] Two winbinds in one machine?
>
>
> Hi,
>
> I'm switching between two domains, and I need to make a couple of
> Linux+Samba machines provide the same shares in both domains. I've set
> up
> two sambas in the same machine, listening on different subinterfaces,
> but I
> can't make winbind to behave properly. As soon as I start the second
> winbind, the domain accounts provided by the first one become hidden
> (that
> is, 'getent passwd' only shows the second domain). I found both winbinds
> use
> the same UNIX socket/pipe. I found no way to choose the socket used, or
> to
> make winbind share the socket, neither in the configure script nor in
> the
> daemon options. Does anyone know how to work around this?
>
> I use samba 2.2.3.
>
>
> Why don't you use 2 different Linux boxes each one acting as a domain
> controller?
>
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
