DRD-Safe Concepts for HP-UX 11i v2 and Later

In addition, the persistent process will have an open file reference to the program it is running,

causing an unmount of the inactive system image to fail.

3.4 Firmware Patches and Other Unsafe Packages

A firmware patch affects both the inactive system image and the booted system image, and as a

result, it is not considered DRD-safe. All firmware patches should exclude themselves from being

installed or removed from within a runcmd environment. This can be accomplished by setting the

is_drd_safe attribute to false for all of its filesets or by adding the following logic to the fileset

level checkinstall and checkremove scripts:

# Check if running in runcmd environment and exclude if

# so because firmware patch cannot be applied within runcmd

# environment.

if [[ $SW_SESSION_IS_DRD -eq 1 ]]

then

msg NOTE “${PRODUCT}.${FILESET} cannot be installed in a DRD

session.”

exit $EXCLUDE

Note that if software is safe to be installed in a DRD environment, but is not safe to be removed, then

is_drd_safe can be set to true and the above method used in the checkremove script.