HP Serviceguard Contributed Toolkit Suite Version A.04.02.02 on Linux User Guide (December, 2012)

Table 16 Files for creating modular packages
Available in directoryDescriptionFile name
$SGCONF/modules/tkit/sambaThis is an attribute definition file, used
to generate a package ASCII template
in modular style of packaging.
samba.1
$SGCONF/scripts/tkit/sambaThis is the module script. This script is
called by the master control script and
tkit_module.sh
acts as an interface between the
tkit_module.sh master control
script and the toolkit interface script
(toolkit.sh). It is also responsible
for calling the toolkit configuration file
generator script.
NOTE: This file is used only for
creating modular packages.
$SGCONF/scripts/tkit/sambaThis is the toolkit configuration file
generator script. This script is called
tkit_gen.sh
by the module script when the
package configuration is applied
using cmapplyconf to generate the
user configuration file in the package
directory TKIT_DIR.
NOTE: This file is used only for
creating modular packages.
Setting up the Samba server in SG/LX environment
Before creating and configuring a Samba SG/LX package, complete the following configuration
tasks for the Samba server application:
1. When the Samba server is installed, the default Samba server may be automatically configured
to be started during system startup via the runlevel (rc) scripts in the /etc/rc.d directory.
Disable the auto-start of a Samba server if the Samba is planed as a SG/LX package on the
running node.
NOTE: If you plan only a single Samba instance running in a cluster, all default configuration
of the standard Samba installation will be fitted into this single instance. You can choose to
modify and use the default configuration file, /etc/samba/smb.conf. Alternatively, you
can generate a new Samba configuration file for the Samba server.
If you want to have multiple Samba instances available and distributed to cluster nodes, you
must create a base configuration file with similar contents as mentioned in the default Samba
configuration.
Additionally, you must create a sub-configuration file that contains Samba configuration for
a specific Samba logic instance. Each individual sub-configuration will be included by the
base configuration and, eventually, the base and sub-configurations becomes a single
configuration file for all Samba logic instances of a single cluster node.
Example of a multiple-instance configuration:
For a two-node cluster, you want to have two Samba instances to distribute to this two cluster
nodes. (Each node owns one Samba instance). Also, you want to share FS1 SMB/CIFS file
system for the first instance and FS2 SMB/CIFS file system for the second instance. You can
modify and use the default Samba configuration file /etc/samba/smb.conf to be a base
configuration file. After that, you must create two sub configuration files for each of the two
instances. The contents of these two sub configuration files are as follows:
For the first instance:
Setting up the Samba server in SG/LX environment 37