Managing Serviceguard Seventeenth Edition, First Reprint December 2009

The length and formal restrictions for the name are the same as for package_name
(page 264). service_name must be unique among all packages in the cluster.
IMPORTANT: Restrictions on service names in previous Serviceguard releases were
less stringent. Packages that specify services whose names do not conform to the above
rules will continue to run, but if you reconfigure them, you will need to change the
name; cmcheckconf and cmapplyconf will enforce the new rules.
Each service is defined by five parameters: service_name, service_cmd, service_restart,
service_fail_fast_enabled, and service_halt_timeout. See the descriptions that follow.
The following is an example of fully defined service:
service_name patricks-package4-ping
service_cmd "/usr/sbin/ping hasupt22"
service_restart unlimited
service_fail_fast_enabled no
service_halt_timeout 300
See the package configuration file for more examples.
For legacy packages, this parameter is in the package control script as well as the
package configuration file.
service_cmd
The command that runs the application or service for this service_name, for example,
/usr/bin/X11/xclock -display 15.244.58.208:0
An absolute pathname is required; neither the PATH variable nor any other environment
variable is passed to the command. The default shell is /usr/bin/sh.
276 Configuring Packages and Their Services