Installation guide
114 Chapter 6:Network File Sharing Services
the specified Windows clients. It also designates access permissions and other mapping capabilities.
In the single system model, a single instance of each of the smbd and nmbd daemons are
automatically started up by the /etc/rc.d/init.d/smb runlevel script.
In order to implement high availibility Samba services, rather than having a single
/etc/samba/smb.conf file; there is an individual per-service samba configuration file. These
files are called /etc/samba/smb.conf.
sharename
; where sharename is the specific name of
the individual configuration file associated with a Samba service. For example, one share could
be called eng and another share acct, the corresponding Samba configuration files would be
/etc/samba/smb.conf.
eng
and /etc/samba/smb.conf.
acct
, respectively.
The format of the smb.conf.
sharename
file is identical to the conventional smb.conf format.
No additional fields have been created for clustered operation. There are several fields within the
smb.conf.
sharename
file which are required for correct cluster operation; these fields will be
described in an upcoming section. When a new Samba service is created using the cluadmin util-
ity, a default template smb.conf.
sharename
file will be created based on the service specific
parameters. This file should be used as a starting point from which the system administrator should
then adjust to add in the appropriate Windows client systems, specific directories to share as well as
permissions.
The system administrator is required to copy the /etc/samba/smb.conf.
sharename
files
onto both cluster members. After the initial configuration time, should any changes be made to any
smb.conf.
sharename
file, it is necessary to also copy this updated version to the other cluster
member.
To facilitate high-availability Samba functionality, each individual Samba service configured within
the cluster (via cluadmin) will have its own individual pair of smbd/nmbd daemons. Consequently,
if there are more than one Samba services configured with the cluster, you may see multiple instances
of these daemon pairs running on an individual cluster server. These Samba daemons smbd/nmbd
are not initiated via the conventional init.d run level scripts; rather they are initiated by the cluster
infrastructure based on whichever node is the active service provider.
In order to allow a single system to run multiple instances of the Samba daemons, each pair of daemons
is required to have its own locking directory. Consequently, there will be a separate per-service Samba
daemon locking directory. This directory is given the name /var/cache/samba/
sharename
;
where sharename is replaced by the Samba share name specified within the service configuration
information (via cluadmin). Following the prior example, the corresponding lock directories would
be /var/cache/samba/
eng
and /var/cache/samba/
acct
.
When the cluadmin utility is used to configure a Samba service, the
/var/cache/samba/
sharename
directory will be automatically created on the system on
which the cluadmin utility is running. At this time a reminder will be displayed that you
need to manually create this lock directory on the other cluster member. For example: mkdir
/var/cache/samba/
eng