Using SAMBA Toolkit in a Serviceguard Cluster README Revision: B.06.00

{
# Stop the HP CIFS Server.
/etc/cmcluster/smb1/toolkit.sh stop
test_return 51
}
5. Configure the user configuration file "hasmb.conf" as explained in
the next section and customize it for your environment.
6. Copy this package configuration directory to all other package
nodes.
You can use the same procedure to create multiple HP CIFS Server
packages (multiple HP CIFS Server instances) that will be managed by
Serviceguard.
D. Setting Up the Toolkit
D.1 Toolkit Overview
After installing the toolkit, four scripts and one README file will be
installed in the location /opt/cmcluster/toolkit/samba. Two more
scripts and one file will be installed which will be used only for
modular packages. The two scripts will be in the
/etc/cmcluster/scripts/ecmt/samba directory. The third file will be in
the /etc/cmcluster/modules/ecmt/samba directory.
For legacy packages, one user configuration script (hasmb.conf) and
three functional scripts (toolkit.sh, hasmb.sh and hasmb.mon) will
work together to integrate the HP CIFS server with the Serviceguard
package
control script.
The scripts used in legacy packages are:
User Configuration file (hasmb.conf)
This script contains a list of pre-defined variables that may be
customized for your environment. This script provides you with a
simple format for (user) configuration data. This file will be
included (that is, sourced) by the toolkit main script (hasmb.sh).
Main Script (hasmb.sh)
This script contains a list of internal-use variables and
functions that support start/stop of a HP CIFS Server instance.
This script will called by the toolkit interface script
(toolkit.sh) to do the following:
- On package start, it starts an HP CIFS Server instance and
launches a monitor process by calling hasmb.mon.
- On package stop, it stops the HP CIFS Server server instance
and halts hasmb.mon.