script changes for proper functioning during a drd

 

 

runcmd execution.

 

 

 

mod_pathfile

Yes

--

mod_systemfile

Yes

--

msg

Yes

--

msg79

Yes

--

newconfig_cp

Yes

--

newconfig_msgs

Yes

--

newconfig_prep

Yes

--

patch_newconfig_cp

Yes

--

patch_newconfig_rollback

Yes

--

patch_newconfig_rollcheck

Yes

--

patch_newconfig_rollsave

Yes

--

patch_newconfig_save

Yes

--

query_systemfile

Yes

The kc* commands called by query_systemfile are

 

 

aware of running during a drd runcmd execution

r_mkdir

Yes

--

strip_off_fr

Yes

--

A.2 HP-UX 11i v2 Commands

The commands used in a control script when SW_SESSION_IS_DRD is set to 1 are limited by the need to be DRD-safe as well as the need to be acceptable for control script use. During a DRD session, restrictions apply to all control scripts except the configure script. This imposes an additional restriction on checkinstall, checkremove, preremove, postremove, and unconfigure scripts, which are less severely restricted during an install to a booted system image.

The following commands may be used in control scripts when SW_SESSION_IS_DRD is set to 1:

•Commands that are part of the POSIX shell, which can be found in the sh-posix(1) man page, EXCEPT FOR kill, which should only be used to modify processes started within the runcmd environment. Using kill on processes started outside of the runcmd environment is not DRD-safe.

•Functions in /usr/lbin/sw/control_utils that are listed as DRD-safe in A.1 HP-UX 11i v2 control_utils.

Commands that are DRD-safe are listed in the table below.

DRD-Safe Commands

Command

DRD-safe

Comments

awk

Yes

--

cat

Yes

--

chgrp

Yes

--

chmod

Yes

--

chown

Yes

--

ch_rc

Yes

--

cmp

Yes

--

cp

Yes

--

efi_cp

Yes

The efi_cp command itself is DRD-safe, however this

 

 

command is often used in conjunction with other logic

 

 

that is not DRD-safe. As such, any control script that