instl_adm.4 (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

instl_adm(4) instl_adm(4)

_hp_root_disk

String variable set by the UI to contain the hardware path or device speciﬁer of the disk you have

chosen to be the root disk. The value is initialized to the value of

_hp_primary_path

/opt/ignite/data/Rel_

release /config and may be overridden in other conﬁguration ﬁles. If

the initial value is not speciﬁed in the conﬁguration ﬁle, it would default to the disk with the

hardware path having the highest SCSI priority.

_hp_root_grp_disks

Integer variable to indicate how many disks to add to the root volume group.

_hp_root_grp_striped

String variable of possible values "YES" and "NO" to indicate if LVM data striping should be used on

all disks in the root volume group if there are multiple disks in the root group.

_hp_saved_detail_level

Internal string variable used in conﬁguration ﬁles that have been created by a "Save-As" operation.

_hp_cfg_detail_level

, it contains a list of option characters that represent which

aspects of the conﬁguration ﬁle have been modiﬁed. The format is identical to the

_hp_cfg_detail_level

variable.

_hp_sec_swap

Integer variable that may be set in the UI to indicate how much secondary swap the user desires to

have allocated in the root volume-group. The default is zero (no secondary swap). If there is more

than one disk in the root volume group, this volume is mapped to the second disk.

_hp_aggregate_lans

String variable set by Ignite-UX with the hardware paths of the interfaces which are conﬁgured into

APA conﬁguration. This variable should not be set or modiﬁed by the user.

_hp_tftp_cmds

String variable that may be speciﬁed in the *INSTALLFS ﬁle to supply additional instructions to

the tftp commands that are used to transfer data during an installation. The commands supplied

with this variable are passed as input to the tftp command along with the usual commands sup-

plied by Ignite-UX. The most likely use of this would be to modify the retransmission-timeout

(rexmt) and overall timeout (timeout) values. The default values that Ignite-UX uses are:

rexmt set to 2 and timeout set to 25. See tftp (1) for more details. The string assigned to this

variable should contain one tftp command statement per line. For example:

init _hp_tftp_cmds="rexmt 5

timeout 40"

Use Model Variables

The conﬁguration ﬁle parser also supports an older version of variables that existed in previous releases.

These are referred to as use models. They are boolean variables in which the variable itself is a string

and its value is either true or false. The variable name is presented in the Additional dialog that is avail-

able in the UI on the Basic tab. The user may toggle the boolean value.

Similar to variables, use models may be made invisible to the UI using the

visible_if keyword.

Ignite-UX does not support the selectable_if or radio_sel keywords that previous releases sup-

ported. The radio_sel functionality is replaced by the ability for regular variables to have a list of

possible values associated with them. Additionally, the help_text keyword for use models has no

effect.

Use models use the same

init keyword as regular variables. When a use model is assigned using the

init keyword, the UI is allowed to change that variable value. An example of how use models are used

is shown below:

init "use_model_name" = TRUE

init "use_model_name" = num_disks > 2

"use_model_name" visible_if (memory > 64MB)

Logic Expressions

A block of conﬁguration statements may be surrounded by a logic expression and a set of {}brackets.

The logic expression may be made up of variables, use models or system attributes. The following logic

operators are recognized (in order of precedence):

8 Hewlett-Packard Company − 8 − HP-UX 11i Version 3: March 2012