The use of multiple server hosting involves running multiple separate instances of Samba, each with it's own
configuration file. This method is complicated by the fact that each instance of nmbd, smbd and winbindd
must have write access to entirely separate TDB files. The ability to keep separate the TDB files used by
nmbd, smbd and winbindd can be enabled either by recompiling Samba for each server hosted so each has its
own default TDB directories, or by configuring these in the
smb.conf file, in which case each instance of
nmbd, smbd and winbindd must be told to start up with its own
smb.conf configuration file.
Each instance should operate on its own IP address (that independent IP address can be an IP Alias).
Each instance of nmbd, smbd and winbindd should listen only on its own IP socket. This can be secured
socket address parameter. Each instance of the Samba server will have its
own SID also, this means that the servers are discrete and independent of each other.
The user of multiple server hosting is non-trivial, and requires careful configuration of each aspect of
process management and start up. The
smb.conf parameters that must be carefully configured includes:
bind interfaces only,
Those who elect to create multiple Samba servers should have the ability to read and follow
the Samba source code, and to modify it as needed. This mode of deployment is considered beyond the scope of
this book. However, if someone will contribute more comprehensive documentation we will gladly review it, and
if it is suitable extend this section of this chapter. Until such documentation becomes available the hosting
of multiple samba servers on a single host is considered not supported for Samba-3 by the Samba Team.