Using SAMBA Toolkit in a ServiceGuard for Linux (SG/LX) Cluster Version A.01.00, June 2003

Using SAMBA Toolkit in a ServiceGuard for Linux (SG/LX) Cluster Version A.01.00
Setting Up SAMBA Server Application for a SG/LX Cluster
Chapter 1 17
D.2 Toolkit User Configuration
All the user configuration variables are kept in a single file in shell script
format. The variable names and their sample values are as follows:
BASE_CONF_FILE (For example:
BASE_CONF_FILE=”/etc/samba/smb.conf”)
This variable holds the base configuration file path. (This file will
contain common configurations for all SAMBA packages in the cluster.)
If not defined, the default value of this variable will be the SAMBA
server directives that are used by all SAMBA instances should be
defined in this file and directives for an individual SAMBA
instanceshould be defined in a sub-configuration file.
SUB_CONF_FILE (For example:
SUB_CONF_FILE=”/usr/local/cmcluster/smb_pkg1/smb.conf”) This
variable holds the configuration file path of a SAMBA instance. Each
SAMBA instance must have its own sub-configuration file that keeps the
definitions that only apply to the specific SAMBA instance. If you want
to have multiple instances running in a cluster, you need to set a value
for this variable.
SMB_SERVICE_NAME (For example:
SMB_SERVICE_NAME=”smb1.monitor”) This variable holds a monitor
process name that represents a ServiceGuard Service. This name should
be identical to the service name defined and registered in a ServiceGuard
Package configuration.
SMB_SERVICE_CMD (For example:
SMB_SERVICE_CMD=”/usr/local/cmcluster/smb_pkg1/hasmb.mon”
) This variable holds a command string to be used for the ServiceGuard
Service. The value of this variable will be the SAMBA toolkit monitor
script name and its parameters.
SMB_SERVICE_RESTART (For example:
SMB_SERVICE_RESTART=”-r 0”) This variable holds a restart option
for the ServiceGuard Service for the monitor service command.
MONITOR_INTERVAL (For example: MONITOR_INTERVAL=6) This
variable holds a time interval (in seconds) for monitoring the SAMBA
instance. That is the monitor process checks the running of smbd and
nmbd daemons every 'interval' seconds. If not defined, its default value
will be 5 seconds.