Managing Serviceguard Sixteenth Edition, March 2009

external_pre_script
The full pathname of an external script to be executed before volume groups and disk
groups are activated during package startup, and after they have been deactivated
during package shutdown (that is, effectively the first step in package startup and last
step in package shutdown). New for modular packages.
If more than one external_pre_script is specified, the scripts will be executed on package
startup in the order they are entered into this file, and in the reverse order during
package shutdown.
See “About External Scripts” (page 184), and the comments in the configuration file,
for more information and examples.
external_script
The full pathname of an external script. This script is often the means of launching and
halting the application that constitutes the main function of the package. New for
modular packages.
The script is executed on package startup after volume groups and file systems are
activated and IP addresses are assigned, but before services are started; and during
package shutdown after services are halted but before IP addresses are removed and
volume groups and file systems deactivated.
If more than one external_script is specified, the scripts will be executed on package
startup in the order they are entered into this file, and in the reverse order during
package shutdown.
See “About External Scripts” (page 184), and the comments in the configuration file,
for more information and examples.
user_name
Specifies the name of a user who has permission to administer this package. See also
user_host and user_role; these three parameters together define the access-control policy
for this package (see “Controlling Access to the Cluster” (page 224)). These parameters
must be defined in this order: user_name, user_host, user_role.
Legal values for user_name are any_user or a maximum of eight login names from
/etc/passwd on user_host.
NOTE: Be careful to spell any_user exactly as given; otherwise Serviceguard will
interpret it as a user name.
Note that the only user_role that can be granted in the package configuration file is
package_admin for this particular package; you grant other roles in the cluster
configuration file. See “Setting up Access-Control Policies” (page 226) for further
discussion and examples.
Choosing Package Modules 283