White Paper

Appendix A
A.1 HP-UX 11i v2 control_utils
The table below describes the SD control_utils, whether they are DRD-safe or not, and any special
information related to DRD that might be of interest to packagers.
DRD-Safe SD control_utils
Function name DRD-
safe
Comments
check_SD_revision
Yes This function was written specifically for use by OS-
Core.UX-CORE. Other packages should not be
using this function.
chmog
Yes --
clean_swlist_output
Yes --
cond_cp
Yes --
cond_cp_set
Yes --
cond_mkdir
Yes --
cp_retain
Yes --
cp_set
Yes --
cu_html
Yes --
cu_hw_scan
Yes --
cu_man
Yes --
cu_obsolete_ancestors
Yes --
cu_run_cmd
Yes --
cu_uniq
Yes --
cu_usage
Yes --
export_master
N/A Defunct for 11i v2 and above
find_ancestor
Yes --
get product_name
Yes --
get_arch
Yes --
get_fileset_name
Yes --
get_install_state
Yes --
get_kernel_path
Yes --
get_os_rev
Yes --
get_owner_group
Yes --
get_sw_rev
Yes --
get_sw_spec
Yes --
get_version
Yes --
Increase_tunable
Yes
--
IPD_addBundleWrapper
Yes --
IPD_addfile
Yes --
IPD_delBundleWrapper
Yes --
IPD_delete_ancestors
Yes --
IPD_delfile
Yes --
is_number
Yes --
is_software_selected
Yes --
kill_named_procs
Yes When kill_named_procs is run during a drd
runcmd execution, it returns 0 without killing any
processes. Packagers need to examine control
scripts calling kill_named_procs () to determine
if not terminating the process requires additional