Fsmountopt, Fsumountopt, Fsfsckopt, Pev | HP Serviceguard specification

fs_mount_opt

The mount options for the file system specified by fs_name. This parameter is in the package control script for legacy packages.

See the mount (1m) manpage for more information.

fs_umount_opt

The umount options for the file system specified by fs_name. This parameter is in the package control script for legacy packages.

Using the-soption of umount will improve startup performance if the package uses a large number of file systems. See the mount (1m) manpage for more information.

fs_fsck_opt

The fsck options for the file system specified by fs_name. Using the-s(safe performance mode) option of fsck will improve startup performance if the package uses a large number of file systems. This parameter is in the package control script for legacy packages.

See the fsck (1m) manpage for more information.

pev_

Specifies a package environment variable that can be passed to an external_pre_script, external_script, or both, by means of the cmgetpkgenv (1m) command. New for modular packages.

The variable name must be in the form pev_<variable_name> and contain only alphanumeric characters and underscores. The letters pev (upper-case or lower-case) followed by the underscore (_) are required.

The variable name and value can each consist of a maximum of MAXPATHLEN characters (1024 on HP-UX systems).

You can define more than one variable. See “About External Scripts” (page 151), as well as the comments in the configuration file, for more information.

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 151), 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.