Managing Serviceguard 14th Edition, June 2007

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 295
Legal value is any number greater than zero. The default is 1.
If the package needs to mount and unmount a large number of
filesystems, you can improve performance by carefully tuning this
parameter during testing (increase it a little at time and monitor
performance each time).
fs_mount_retry_count The number of mount retries for each file
system.
Legal value is zero or any greater number. The default is zero.
If the mount point is busy at package startup and
fs_mount_retry_count is set to zero, package startup will fail.
If the mount point is busy and fs_mount_retry_count is greater than
zero, the startup script will attempt to kill the user process responsible
for the busy mount point (fuser -ku) and then try to mount the file
system again. It will do this the number of times specified by
fs_mount_retry_count.
If the mount still fails after the number of attempts specified by
fs_mount_retry_count, package startup will fail.
This parameter is in the package control script for legacy packages. See
“Configuring a Legacy Package” on page 363.
fs_umount_retry_count The number of umount retries for each file
system. Replaces FS_UMOUNT_COUNT, which is still supported in the
package control script for legacy packages; see “Configuring a Legacy
Package” on page 363.
Legal value is any greater number greater than zero. The default is 1.
Operates in the same way as fs_mount_retry_count (see page 295).
fs_name This parameter, in conjunction with fs_directory, fs_type,
fs_mount_opt, fs_umount_opt, and fs_fsck_opt, specifies a filesystem
that is to be mounted by the package. Replaces LV, which is still
supported in the package control script for legacy packages.
fs_name must specify the block devicefile for a logical volume.
Filesystems are mounted in the order specified in this file, and
unmounted in the reverse order. See the comments in the FILESYSTEMS
section of the configuration file for more information and examples.
See also “Logical Volume and File System Planning” on page 165, and
the mount (1m) manpage.