Ignite-UX Custom Configuration files

You can now use the instl_dbg command to print out the fully parsed configuration (The –D
option points it to a per-client directory containing the files it needs. The –f option designates
where to write the parsed configuration). This will occur with and without the config file being
present in the per-client directory:
# instl_dbg -D . -f /tmp/client.with.config
# mv config config.save
# instl_dbg -D . -f /tmp/client.with.no.config
With the per-client config file present, the cfg clause 2003-10-08,12:45 Recovery
Archive is selected:
# head /tmp/client.with.config
cfg "2003-10-08,12:45 Recovery Archive"=TRUE
server="10.0.0.3"
is_net_info_temporary=FALSE
init _hp_keyboard="PS2_DIN_US_English"
system_name="host"
ip_addr[]="10.0.0.1"
netmask[]="0xffffff00"
route_gateway[0]="10.0.0.2"
route_destination[0]="default"
_hp_cfg_detail_level="ibnpvcdsrlLtfh"
...
Without the per-client config file present, the cfg clause is selected by the CINDEX file (2003-
10-08,12:41 Recovery Archive) instead:
# head /tmp/client.with.no.config
cfg "2003-10-08,12:41 Recovery Archive"=TRUE
server="10.0.0.3"
is_net_info_temporary=FALSE
init _hp_keyboard="PS2_DIN_US_English"
system_name="host"
ip_addr[]="10.0.0.1"
netmask[]="0xffffff00"
route_gateway[0]="10.0.0.2"
route_destination[0]="default"
_hp_cfg_detail_level="ibnpvcdsrlLtfh"
...
The instl_dbg command is covered in more detail in a later section.
What is in a configuration (cfg) clause?
The question now is, what is in a cfg clause? The following example shows a cfg clause taken
from the /var/opt/ignite/INDEX file:
cfg "HP-UX B.11.11 Default" {
description "This selection supplies the default system configuration
that HP supplies for the B.11.11 release."
"/opt/ignite/data/Rel_B.11.11/config"
"/opt/ignite/data/Rel_B.11.11/hw_patches_cfg"
"/var/opt/ignite/config.local"
}=TRUE
13