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 114
Setting Up SAMBA Toolkits Running SAMBA Server Packages
D.1 Toolkit Overview
After installing the toolkit, four scripts and one README file will
installed.
• In a RedHat environment, the toolkit will be installed in
/usr/local/cmcluster/sambatoolkit
• In a SLES 8/UL environment, the toolkit will be installed in
/opt/cmcluster/sambatoolkit
One user configuration script (hasmb.conf) and three functional scripts
(toolkit.sh, hasmb.sh, and hasmb.mon) will work each other to provide
full functionality of a HA SAMBA server. These scripts are:
User Configuration file (hasmb.conf)
This script contains a list of pre-defined variables that the toolkit user
must assign proper values on them. No function, running script
statement is in this file. This script purely provides the user a
none-confused and simple format of user configuration data and,
eventually, will be included by a toolkit main script in order to run
toolkit functions. This script includes all user configuration variables
features specified in above section and it is the only toolkit interface to
the user.
Main Script (hasmb.sh)
This script contains a list of internal-use variables and functions
thatsupport start/stop of a SAMBA instance. This script will called by
the Toolkit Interface Script and do the following:
On package start, it starts an SAMBA server instance and launches a
monitor process by calling the SAMBA monitor script.
On package stop, it stops the SAMBA server instance and halts the
monitor process.
Monitor Script (hasmb.mon)
This script contains a list of internal-use variables and functions for
monitoring a SAMBA server instance. This script will be called by the
Toolkit Main Script and will constantly monitor two SAMBA daemons,
smbd and nmbd:
Interface Script (toolkit.sh)