How to avoid side effect between critical and non critical services in a package ?

[Gousset]

Hi,

I have defined a package hosting 2 services : SERVICE[0] which is critical, and SERVICE[1]which is not. I have defined SERVICE_RESTART[0]="", and SERVICE_RESTART[1]="-r 3". The problem here is that when SERVICE[1] has restarted 3 times, it will make the make package switch, interrupting the critical SERVICE[0] during the switch.
Is there any configuration that would permit to avoid the switch when SERVICE[1] has reached its max number of restart ?

ThX in advance,
BR

[Steven E. Protter]

Shalom,

Configure them in three independent packages.

SEP

[Serviceguard for Linux]

You may also want to look at the new package features in the 11.18 version of Serviceguard. The docs for the HP-UX version are posted http://docs.hp.com/en/ha.html. The Linux version will be available in July.

[Stephen Doud]

You have a package that has 2 services, which are either essential to the operation of the package, or they both determine the operational status of the package.

However per you message, one service is not as critical as the other and may actually interfere with the continued operation of the package.
My question is, why use the 2nd service if if is not as critical?

In any case, when a SERVICE approaches the MAX_RESTARTS value, you can reset it if you wish. The man page shows the format:
cmmodpkg [-v] -R -s service_name package_name

Reset the restart counter for service SVC1 in package PKG1.

cmmodpkg -R -s SVC1 PKG1

Or you may simply change the SERVICE_RESTARTS parameter in the package control script to "-R" and it will restart infinitely and never interfere with package operation - which goes back to, what is the point of creating a service that you don't really want to control package operation.