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 118
RETRY_TIMES (For example: RETRY_TIMES=3) This variable holds
the number of times to attempt to check the SAMBA daemons before
giving up and exiting to fail state. If not defined, its default value will be
2 times.
The following procedures will show you the steps to configure a SAMBA
toolkit running the SAMBA package. This includes configuring the
SAMBA toolkit user configuration file.
Note: Before working on the toolkit configuration, the package directory
(e.g. /usr/local/cmcluster/smb_pkg1) must be created and all toolkit
scripts are copied to the package directory.
1. Edit the SAMBA Toolkit user configuration file.
On the package directory, edit the user configuration file (hasmb.conf) as
indicated by the comments in that file. You may want to keep the
variable default values.
For example:
BASE_CONF_FILE=”/etc/samba/smb.conf”
SUB_CONF_FILE=”/usr/local/cmcluster/smb_pkg1/smb.conf”
SMB_SERVICE_CMD=”smb1.monitor”
SMB_SERVICE_CMD=”/usr/local/cmcluster/smb_pkg1/hasmb.mon”
SMB_SERVICE_RESTART=”-r 0
2. Distribute all package files of the package directory to the planned
package nodes. All planned nodes should have identical file path for all
package files. For this example, each package node must have the
following files in the package directory:
smb_pkg.conf#Package configuration file
smb_pkg.cntl#Package control file
hasmb.conf#SAMBA toolkit user configuration file
hasmb.mon#SAMBA toolkit monitor program
hasmb.sh#SAMBA toolkit main script
toolkit.sh#Interface file between the package control file and
the toolkit.