HP Serviceguard Contributed Toolkit Suite Version A.04.02.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction...............................................................................................6 Storage considerations..............................................................................................................6 Installing and uninstalling the Contributed Toolkits.........................................................................6 2 Apache Toolkit...........................................................................................8 Overview.............
Using PostgreSQL toolkit..........................................................................................................30 Configuring PostgreSQL toolkit packages...............................................................................31 Configuring legacy PostgreSQL toolkit packages................................................................31 Configuring modular PostgreSQL toolkit packages.............................................................32 Managing packages.................
Local configuration.............................................................................................................55 Shared configuration..........................................................................................................55 Multiple Tomcat Instances Configuration...............................................................................55 Using Tomcat toolkit...............................................................................................................
1 Introduction The HP Serviceguard Contributed Toolkit Suite is a collection of toolkits for popular applications to integrate them with the HP Serviceguard for Linux (SG/LX) environment. This toolkit suite is available as a tar file, which you must extract to get the RPM of each toolkit bundled with this suite.
To remove the earlier version, run the following command: # rpm –e > To ensure that the toolkit is removed from all the configured nodes of the cluster, run the following command: # rpm –qa | grep Installing and uninstalling the Contributed Toolkits 7
2 Apache Toolkit Overview HP Serviceguard toolkit for Apache on Linux (Apache toolkit) enables you to integrate the Apache web server application with HP Serviceguard. Using Apache toolkit simplifies application integration, and eases deployment and maintenance of the application in a Serviceguard cluster environment. The Apache toolkit consists of a set of scripts that are used to start, stop, and monitor the Apache web server application. The toolkit simplifies the task of integrating Apache with SG/LX.
Files and directories created for Apache toolkit after installation The following table describes the scripts installed as part of the Apache toolkit installation. Table 1 Files created after Apache toolkit is installed File name Description Available in directory hahttp.conf This is the toolkit configuration file. It $SGROOT/apachetoolkit contains a list of pre-defined variables that must be set for your unique environment. hahttp.
1. 2. When the Apache server is installed, the default Apache instance might be configured to automatically startup during system startup via the runlevel (rc) scripts in the /etc/rc.d directory. In such a case, disable the automatic startup of Apache. Configure the Apache server. For more information about configuring the Apache server, see Apache Web Server documentation. 3. Create a separate, distinct server root directory and server configuration file for each Apache SG/LX package.
node in the cluster. However, you must ensure that the mount point of the shared file system is identical across all Apache toolkit package nodes. NOTE: HP recommends that you use the shared configuration option for configuring this toolkit because you do not have to maintain identical copies of the files and directories on all the nodes. The information is automatically accessible to all the nodes.
1. 2. 3. 4. 5. 6. Create a volume group vgtry1 on shared storage. Create a logical volume lvol in vgtry1. Create a filesystem on the logical volume lvol. Create a directory /mnt/vgtry1/apache on the local disk. Mount device /dev/vgtry1/lvol to the /mnt/vgtry1/apache. Copy all the files from the server root to /mnt/vgtry1/apache. To configure a single instance: 1. For the Apache toolkit package to run, create a directory, such as $SGCONF/pkg/apache1.
Initialize the RUN_SCRIPT and the HALT_SCRIPT in the package control script. Table 4 (page 13) lists all the variables that you can edit based on the requirement of your environment. Table 4 List of variables that you can edit 3. Variable Example RUN_SCRIPT $SGCONF/pkg/apache1/pkg.cntl RUN_SCRIPT_TIMEOUT NO_TIMEOUT HALT_SCRIPT $SGCONF/pkg/apache1/pkg.
test_return 51 } c. To halt the Apache toolkit package, add the following line to the customer_defined_halt_cmds function of the control script: function customer_defined_halt_cmds { $SGCONF/pkg/apache1/toolkit.sh stop test_return 52 } NOTE: You must select a package IP address that is not used by any other application. Serviceguard cannot start a package if the IP address corresponding to the package is already in use. 4. 5. Edit the Apache toolkit configuration file hahttp.conf.
1. Configure volume groups for each Apache instance. To create volume groups applicable for both shared and local configuration: a. Create another volume group, such as vgtry2. b. Create a logical volume lvol in the volume group that you just created. c. Create a file system on this logical volume and mount it. For example: /mnt/vgtry2/apache d. Copy all the files from the server root directory to /mnt/vgtry2/apache. 2. Create another package directory.
6. To configure the PID_FILE parameter with the path for pid file for the corresponding instance, run: PID_FILE="$SGCONF/pkg/apache2/httpd_s1.pid" 7. To edit the listen parameter in the httpd.conf file such that the specified port is not being listened to by any other application, run: Listen . 8. 9. Edit the corresponding httpd.conf file, and the other Apache configuration files placed in the server root directory. Copy the package directory to the other nodes in the cluster.
Table 6 List of attributes that you can edit (continued) Attribute Description NOTE: • Set the ServerRoot directive in this file as per the requirement. • Apache toolkit does not support online modification of this attribute. • On RHEL, the default configuration file is /etc/ httpd/conf/httpd.conf. • On SLES, the default configuration file is /etc/apache2/httpd.conf. FAIL_CRITERIA Fail criteria for monitoring the Apache processes.
Table 6 List of attributes that you can edit (continued) Attribute Description NOTE: If the Maintenance flag is set to no, then this feature does not work. MONITOR_INTERVAL The time interval in seconds to monitor the Apache server instance. The default value is 30. RETRY_TIMES The number of trials attempted by the toolkit script to check the Apache server daemon before giving up and exiting. The default value is 0. vg The volume group created for this package.
The toolkit monitoring script stops monitoring the Apache daemons running for the instance configured for the package. The following message is logged in the package control script: Apache toolkit pausing, monitoring, and entering maintenance mode. 3. Perform the maintenance actions. For example, you can change the configuration of the Apache instance or install an Apache patch. 4. To start monitoring application processes, run: # rm -f $SGCONF/pkg/apache1/apache.
3 MySQL Toolkit Overview HP Serviceguard toolkit for MySQL on Linux (MySQL toolkit) enables you to configure MySQL database server application in an SG/LX cluster environment. The MySQL toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the MySQL database server. The toolkit simplifies the task of integrating MySQL with SG/LX.
Table 8 Files for creating modular packages File name Description Available in directory mysql.1 This is an attribute definition file used $SGCONF/modules/tkit/mysql to generate a package ASCII template in modular style of packaging. tkit_module.sh This is the module script. This script is $SGCONF/scripts/tkit/mysql called by the master control script and acts as an interface between the tkit_module.sh master control script and the toolkit interface script (toolkit.sh).
NOTE: • Since each database instance resides in its own filesystem, multiple database instances can be configured in the environment using this method. • In the case of MySQL version for SLES, mysqld_safe is known as safe_mysqld. Hence, you have to modify the suitable sections in the my.cnf file. • The mysqld_multi feature of MySQL is not supported with MySQL toolkit on SLES system. Use separate MySQL toolkit packages for each instance of MySQL.
Configuring legacy MySQL toolkit packages To configure legacy MySQL toolkit packages: 1. Create a directory for the package on all the cluster nodes using the following command: # mkdir $SGCONF/pkg/MySQL 2. 3. 4. Copy the toolkit files from $SGROOT/mysqltoolkit to the package directory $SGCONF/pkg/MySQL. cd to the package directory. Create the package configuration and control templates using the cmmakepkg command: Configuration template: # cmmakepkg -p pkg_MySQL.
$SGCONF/pkg/MySQL/toolkit.sh start test_return 51 } To run the toolkit.sh script with the start option, edit the customer_defined_halt_cmds function in the package control script as follows: function customer_defined_halt_cmds { $SGCONF/pkg/MySQL/toolkit.sh stop test_return 52 } 6. 7. Edit the MySQL toolkit configuration file hamysql.conf. Copy the package directory to the other nodes in the cluster.
Table 10 Lists the attributes that you can edit (continued) Attribute Description CONFIGURATION_FILE_PATH share/mysql/ my.cnf NOTE: MySQL toolkit does not support online modification of this attribute. PID_FILE PID file of main MySQL process belongs to this package. This PID file, if present in the my.cnf, must correspond to the pid-file option on the configuration file. The PID file must be in the local hard disk. For example, PID_FILE /var/run/mysqld1.
6. Create the package using the cmapplyconf command, if the cmcheckconf command does not report any errors: # cmapplyconf -P pkg_MySQL.conf 7. Enable package switching for the MySQL toolkit package using: # cmmodpkg -e -n node1 -n node2 # cmmodpkg -e 8. Start the package using the cmrunpkg command. # cmrunpkg Managing packages You can manage packages by running, maintaining, halting, and deleting them.
NOTE: Ensure that the MySQL server instance is up and running before removing the mysql.debug file. Halting packages To halt a package: # cmhaltpkg Deleting packages To delete a package from the cluster: # cmdeleteconf -p This command prompts for a verification before deleting the files, unless you use the -f option.
4 PostgreSQL Toolkit Overview HP Serviceguard toolkit for PostgreSQL on Linux (PostgreSQL toolkit) enables you to integrate the PostgreSQL database server with HP Serviceguard. Using PostgreSQL toolkit simplifies application integration, and eases deployment and maintenance of applications in a cluster environment. The PostgreSQL toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the PostgreSQL database server.
Table 12 Files for creating modular packages File name Description Available in directory pgsq.l This is an attribute definition file, used $SGCONF/modules/tkit/pgsql to generate a package ASCII template in modular style of packaging. tkit_module.sh This is the module script. This script is $SGCONF/scripts/tkit/pgsql called by the master control script and acts as an interface between the tkit_module.sh master control script and the toolkit interface script (toolkit.sh).
tcpip_socket = true # Allows the client connection over the network port = 5433 # Select a unique port number for each of the # PostgreSQL toolkit Packages The presence of parameter tcpip_socket is dependent on the version of postgresql supported by the distro. The newer versions of postgresql have replaced the parameter tcpip_socket by listen_address. Depending on the parameter supported by PostgreSQL, configure tcpip_socket=true or listen_addresses.
Configuring PostgreSQL toolkit packages You can configure PostgreSQL toolkit packages using either legacy or modular style of packaging. Configuring legacy PostgreSQL toolkit packages To configure legacy PostgreSQL toolkit packages: 1. Create a directory for the package on all the cluster nodes using the following command: # mkdir $SGCONF/pkg/postgresql 2. 3. 4. Copy the toolkit files from $SGCONF/postgresqltoolkit to the package directory $SGCONF/pkg/postgresql. cd to the package directory.
Table 13 List of attributes that you can edit (continued) Attribute Description Example If the value is a positive integer, the service is restarted for the specified number of times before failing. If service_restart is not specified, the default value is none. 6. To execute the toolkit.sh script with the start option, edit the customer_defined_run_cmds function in the package control script as follows: For example: function customer_defined_run_cmds { # Start the PostgreSQL Database Server.
1. Create a directory for the package on all the cluster nodes using the following command: # mkdir $SGCONF/pkg/pgsql 2. 3. cd to the package directory. Create the package configuration and control templates using the cmmakepkg command: # cmmakepkg –m tkit/pgsql/pgsql pgsql_pkg.conf 4. Edit the following attributes manually in the package configuration file. Table 14 (page 33) lists all the attributes that you can edit manually in the package configuration file.
5. Validate the configuration using the cmcheckconf command: # cmcheckconf -P pgsql_pkg.conf 6. Create the package using the cmapplyconf command, if the cmcheckconf command does not report any errors: # cmapplyconf -P pgsql_pkg.conf Managing packages You can manage packages by running, maintaining, halting, and deleting them.
Halting packages To halt a package: # cmhaltpkg Deleting packages To delete a package from the cluster: # cmdeleteconf -p This command prompts for a verification, before deleting the files, unless you use the -f option.
5 Samba Toolkit Overview HP Serviceguard toolkit for Samba on Linux (Samba toolkit) enables you to configure Samba in an SG/LX cluster environment. The Samba toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the Samba database server. The toolkit simplifies the task of integrating Samba with SG/LX. Advantages When Samba toolkit is deployed in an SG/LX environment, following are the advantages: • Provides monitoring for Samba daemons.
Table 16 Files for creating modular packages File name Description Available in directory samba.1 This is an attribute definition file, used $SGCONF/modules/tkit/samba to generate a package ASCII template in modular style of packaging. tkit_module.sh This is the module script. This script is $SGCONF/scripts/tkit/samba called by the master control script and acts as an interface between the tkit_module.sh master control script and the toolkit interface script (toolkit.sh).
[FS1] comment path valid users public writable printable create mask = = = = = = = File System 1 /shared/FS1 user1 yes yes no 0765 = = = = = = = File System 2 /shared/FS2 user2 yes yes no 0765 For the second instance: [FS2] comment path valid users public writable printable create mask 2. Create a separate, distinct sub configuration file for each Samba SG/LX package. Each package corresponds to a unique Samba logic instance with its associated sub configuration file.
NOTE: When a Samba toolkit package is extended to one or more additional nodes, the same SMB or CIFS file system and configuration file structure must be used on all nodes, regardless of whether this is a local or a shared configuration. For a Samba local or shared configuration: • Each node must have the same version of the Samba application.
1. Create a directory for the package on all the cluster nodes using the following command: # mkdir $SGCONF/pkg/samba 2. 3. 4. Copy the toolkit files from $SGROOT/sambatoolkit to the package directory $SGCONF/ pkg/samba. cd to the package directory. Create the package configuration and control templates using the cmmakepkg command: Configuration template: # cmmakepkg -p smb_pkg.conf Control template: # cmmakepkg -s smb_pkg.cntl 5.
Table 17 List of attributes that you can edit (continued) Attribute Description Example HA_APP_SERVER This parameter provides high availability to the Samba server by uncommenting this parameter. pre-IP For example, HA_APP_SERVER=“pre-IP” SERVICE_NAME[0] The service name must be unique in smb1_monitor the cluster. SERVICE_CMD[0] This is an interface to hasmb.sh. SERVICE_RESTART[0] The value for service_restart -r 0 can be unlimited, none or any positive integer value.
# cmmodpkg -e smb_pkg 11. Start the package using the cmrunpkg command. # cmrunpkg smb_pkg Configuring Samba modular packages To configure modular Samba toolkit packages: 1. Create a directory for the package on all the cluster nodes using the following command: # mkdir $SGCONF/pkg/samba 2. 3. cd to the package directory. Create the package configuration and control templates using the cmmakepkg command: # cmmakepkg –m tkit/samba/samba smb_pkg.conf 4.
Table 18 List of attributes that you can edit (continued) Attribute Description If the file exists, monitoring is paused, and you can bring down Samba for maintenance. The package does not fail over to the adoptive node even though Samba instance is brought down for maintenance. After the maintenance work, ensure that Samba is brought up. You must delete the samba.debug file in the package directory. This enables the toolkit to continue monitoring Samba server application.
The toolkit monitoring script stops monitoring the Samba daemons running for the instance configured for the package. The following message is logged in the package control script: Samba toolkit pausing, monitoring, and entering maintenance mode. 3. Perform the maintenance actions. For example, you can change the configuration of the Samba instance, or install a Samba patch. 4. To start monitoring application processes, run the following command: # rm -f $SGCONF/pkg/SMB_1/samba.
6 Sendmail Toolkit Overview HP Serviceguard toolkit for Sendmail on Linux (Sendmail toolkit) enables you to configure Sendmail in an SG/LX cluster environment. The Sendmail toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the Sendmail server. The toolkit simplifies the task of integrating Sendmail with SG/LX. Sendmail application must be installed on all nodes that runs the Sendmail application in the SG/LX cluster.
Table 19 Files created after Sendmail toolkit is installed File name Description Available in directory hasendmail.conf This is the toolkit configuration file. It $SGROOT/sendmailtoolkit contains a list of pre-defined variables that needs to be set to run the Sendmail toolkit package. hasendmail.sh This is the toolkit main script that contains internal functions that start or stop an Sendmail server instance. hasendmail.mon This monitors the health of the running Sendmail server application.
NOTE: 3. • The configuration file is read once when the Sendmail application starts up. Any subsequent changes to this file after the Sendmail application is up does not take effect until the Sendmail is restarted. • On SLES systems the default sendmail.mc file does not exist. For more information about customizing and building /etc/sendmail.cf, see http://www.sendmail.org/. Disable the Sendmail application auto-startup on all the cluster nodes: For example: • On Red Hat: # mv /etc/rc.d/rc5.
Local configuration In a typical local configuration, all file systems are shared between the nodes. Identical copies of the Sendmail server configuration files reside in exactly the same locations of a local storage on each node. You must ensure to maintain identical copies of the Sendmail components on the different nodes. Shared configuration In shared configuration, the file systems and configuration files are placed on the shared storage.
Table 21 List of attributes that you can edit (continued) Attribute Description Example HALT_SCRIPT This is the script to halt the service. $SGCONF/pkg/Sendmail/ pkgsm.cntl SERVICE_NAME The service name must be unique in pkgsm_service the cluster. Control Script Parameters VG[0] The VG created for this package. /dev/vgSM LV[0] The logical volume created in VT. /dev/vgSM/lvol FS[0] This is the file system for DB. /pkgSM FS_TYPE[0] The FS type is Extended 2.
test_return 52 } 6. 7. Edit the sendmail the toolkit configuration file hasendmail.conf. Copy the package directory to the other nodes in the cluster. For example, change to the parent directory of the package directory and enter the following command: # rcp -r –p $SGCONF/pkg/Sendmail node2:$PWD/ 8. Validate the configuration using the cmcheckconf command: # cmcheckconf -P pkgsm.conf 9.
Table 22 List of attributes that you can edit (continued) Attribute Description NOTE: Sendmail toolkit does not support online modification of this attribute. QUEUE QUEUE can be set to a time interval that the Sendmail can process the queued mails in the mail queue directory, for example 1h for 1 hour interval. NOTE: Sendmail toolkit does not support online modification of this attribute. MAINTENANCE_FLAG This is used to bring this toolkit into maintenance mode.
Maintaining packages HP Serviceguard normally monitors critical processes, but there might be situations when a planned maintenance task (for example, changing the configuration) is required that affects those monitored processes. The maintenance flag can be used to signal to Serviceguard that it must not failover the instance to an adoptive node.
7 Tomcat Toolkit Overview HP Serviceguard toolkit for Tomcat on Linux (Tomcat toolkit) enables you to configure Tomcat server in an SG/LX cluster environment. The Tomcat toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the Tomcat database server. The toolkit simplifies the task of integrating Tomcat with SG/LX.
Table 24 Files for creating modular packages File name Description Available in directory tomcat.1 This is an attribute definition file, used $SGCONF/modules/tkit/tomcat to generate a package ASCII template in modular style of packaging. tkit_module.sh This is the module script. This script is $SGCONF/scripts/tkit/tomcat called by the master control script and acts as an interface between the tkit_module.sh master control script and the toolkit interface script (toolkit.sh).
Local configuration Tomcat data and configuration files are present on the local disk on all the nodes is enabled for the Tomcat toolkit package. The data and configuration files must be identical across all the nodes configured for the Tomcat toolkit package in the cluster and it must be available on the same location. If you make any change to the database, you must replicate the same change to all the nodes.
Table 25 List of attributes that you can edit Attribute Description Example PACKAGE_NAME The package name must be unique in the cluster. tomcat_pkg1 NODE_NAME The name of the node that runs the package. node1 RUN_SCRIPT This is the script to start the service. $SGCONF/pkg/Tomcat/ tomcat_pkg.cntl HALT_SCRIPT This is the script to halt the service. $SGCONF/pkg/Tomcat/ tomcat_pkg.cntl service_name The service name must be unique in tomcat1_monitor the cluster.
test_return 52 } 6. 7. Edit the tomcat the toolkit configuration file, hatomcat.conf. Copy the package directory to the other nodes in the cluster. For example, change to the parent directory of the package directory and enter the following command: # rcp -r –p $SGCONF/pkg/Tomcat node2:$PWD/ 8. Validate the configuration using the cmcheckconf command: # cmcheckconf -P tomcat_pkg.conf 9.
Table 26 List of attributes that you can edit (continued) Attribute Description TOMCAT_USER The userid used to start the tomcat daemon. It can be either www or root. No other user can start tomcat. It is advisable that tomcat is not started as root since it may lead to security vulnerabilities. NOTE: Tomcat toolkit does not support online modification of this attribute. JAVA_HOME Base directory of Java Development kit. This software is a pre-requisite for running Tomcat.
Maintaining packages HP Serviceguard normally monitors critical processes, but there might be situations when a planned maintenance task (for example, changing the configuration) is required that affects those monitored processes. The maintenance flag can be used to signal to Serviceguard that it should not failover the instance to an adoptive node.
8 Online Modification of the Toolkit package In addition to the Online modification feature supported by Serviceguard, the online modification feature of the toolkit allows you to modify some of the toolkit attribute values, while the toolkit package is running. For more information about the list of attributes that support online modification for a specific toolkit package, see the Attribute definition table in Configuring modular toolkit packages of that Toolkit. To perform online package modification: 1.
9 Troubleshooting This section explains some of the problem scenarios that you might encounter while working with the Contrib toolkit in an SG/LX cluster. Table 27 lists the problem scenarios that you might encounter while working with the Contrib toolkit in an SG/LX cluster.
10 Support and other resources Information to collect before contacting HP Ensure that the following information is available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP HP provides the HP Serviceguard Contributed Toolkit Suite on Linux for free, so there is no support for it.
Term A term or phrase that is defined in the body text of the document, not in a glossary. User input Indicates commands and text that you type exactly as shown. Replaceable The name of a placeholder that you replace with an actual value. [] In command syntax statements, these characters enclose optional content. {} In command syntax statements, these characters enclose required content. | The character that separates items in a linear list of choices. ...
A Sample Apache toolkit package configuration file 64 package_name package_description package_type node_name script_log_file kit/apache/apache/TKIT_DIR tkit/apache/apache/HTTPD_CONFIG_FILE tkit/apache/apache/PID_FILE tkit/apache/apache/FAIL_CRITERIA tkit/apache/apache/MAINTENANCE_FLAG tkit/apache/apache/MONITOR_INTERVAL apache_pkg "Serviceguard Package" failover * $SGCONF/apache_pkg/$SG_PACKAGE.log $SGCONF/apache_pkg /etc/httpd/conf/httpd.conf_1 /var/run/httpd.
B Sample MySQL toolkit package configuration file package_name package_description package_type node_name script_log_file tkit/mysql/mysql/TKIT_DIR tkit/mysql/mysql/CONFIGURATION_FILE_PATH tkit/mysql/mysql/PID_FILE tkit/mysql/mysql/MAINTENANCE_FLAG tkit/mysql/mysql/RETRY_TIMES tkit/mysql/mysql/MONITOR_INTERVAL tkit/mysql/mysql/TIME_OUT service_name service_cmd service_restart service_fail_fast_enabled service_halt_timeout priority vgchange_cmd vg fs_name fs_server fs_directory fs_type fs_mount_opt mysql_pk
C Sample PostgreSQL toolkit package configuration file package_name package_description package_type node_name script_log_file tkit/pgsql/pgsql/TKIT_DIR tkit/pgsql/pgsql/DATA_DIRECTORY tkit/pgsql/pgsql/LOG_FILE tkit/pgsql/pgsql/MAINTENANCE_FLAG tkit/pgsql/pgsql/MONITOR_INTERVAL service_name service_cmd service_restart service_fail_fast_enabled service_halt_timeout vg fs_name fs_server fs_directory fs_type fs_mount_opt 66 Sample PostgreSQL toolkit package configuration file pg_pkg "Serviceguard PostgreSQ
D Sample Samba toolkit package configuration file package_name package_description package_type node_name script_log_file smb_pkg "Serviceguard samba toolkit Package" failover * $SGCONF/smb_pkg/$SG_PACKAGE.log tkit/samba/samba/TKIT_DIR tkit/samba/samba/BASE_CONF_FILE tkit/samba/samba/MAINTENANCE_FLAG tkit/samba/samba/MONITOR_INTERVAL $SGCONF/smb_pkg /etc/samba/smb.conf yes 30 service_name service_cmd samba.monitor "$SGCONF/scripts/tkit/samba/tkit_module.
E Sample Sendmail toolkit package configuration file package_name package_description package_type node_name script_log_file sendmail_pkg "Serviceguard sendmail toolkit Package" failover * $SGCONF/sendmail_pkg/$SG_PAC KAGE.
F Sample Tomcat toolkit package configuration file package_name package_description package_type node_name script_log_file tom_pkg "Serviceguard tomcat toolkit Package" failover * $SGCONF/$SG_PACKAGE.
Glossary $SGCONF /opt/cmcluster/conf for SLES /usr/local/cmcluster/conf for Red Hat $SGROOT /opt/cmcluster for SLES /usr/local/cmcluster for Red Hat ADF Attribute definition file CIFS Common Internet File System Package A grouping of application services (individual Linux Processes) under Serviceguard SLES SUSE Linux Enterprise Server SMB Server Message Block VG Volume Group 70 Glossary
Index A Apache Toolkit Advantages, 8 Overview, 8 Prerequisites, 8 Apache toolkit after Installation files and directories, 9 H HP Serviceguard Contributed Toolkit Suite Introduction, 6 troubleshooting, 61 M Managing packages halting packages, 19, 27, 35, 44, 52, 59 maintaining packages, 59 running packages, 18, 26, 34, 43, 51, 58 S Storage considerations, 6 Supported configuration, 10 T Tomcat Toolkit Managing packages, 58 typographic conventions, 62 71
