Serviceguard
cancel
Showing results for 
Search instead for 
Did you mean: 

using a legacy control script (and the toolkit) to integrate an app

joseph pareti
Frequent Advisor

using a legacy control script (and the toolkit) to integrate an app

I am using SGLX A 11.18 on rhel4 and I would like to integrate an app in the package. According to the "Managing HP SG for Linux, 7th edition" guide, the way to do it, is by using a "legacy package" (the terminology is IMO somehow misleading), and to use the RUN_SCRIPT, HALT_SCRIPT entries in the package configuration file. My question is that these entries were not created for me whan I ran
# cmmakepkg $SGCONF/pkg1/pkg1.conf

In addition, there is a whitepaper "Framework for HP Serviceguard Toolkits" explaining the integration: appendix B lists a sample integration with MySQL, and also refers to RUN_SCRIPT, HALT_SCRIPT in the pkg config. file.

Is it correct to go ahead and edit pkg1.conf ?

Why does it not get set by cmmakepkg?
Or am I missing anything else?
1 REPLY
melvyn burnard
Honored Contributor

Re: using a legacy control script (and the toolkit) to integrate an app

The term "legacy package" refers to the package scirpt/configuration files used PRIORto A.11.18 of Serviceguard.
The newest version uses a newer method, referred to as the UPCC.

As far as cmmakepkg, you use the -p option to create your configuration template file, and the -s option to create your script or control file template.
These BOTH need to be edited to have the correct information in them, and the RUN_SCRIPT, HALT_SCRIPT entries in the package configuration file are used to refer to the control script you create. They are NOT Their by default because you can name the file anything you want to.

BTW:
I have assigned points to 2 of 18 responses to my questions.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!