Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

from the Ignite-UX GUI using the Additional Configuration Controls dialog box. For more information
see the section “Additional... Button” (page 124).
To specify this option at the global level (for example in the /var/opt/ignite/config.local
file), you can add the following line:
sd_command_line += " -xpatch_save_files=false "
To default the variable controlling the operating system patches to “no”, add the following to
config.local, which must be listed after hw_patches_cfg in the /var/opt/ignite/data/
INDEX file:
init _hp_patch_save_files = "NO"
For more details, see the "Managing Patches" chapter in the Software Distributor Administration
Guide and the Patch Management User Guide for HP-UX 11.x Systems.
Debugging Configuration Files
Designing a configuration file to meet your needs can be a very tedious task. It usually requires a
lot of trial and error. You will need to install systems to test your configuration files. The instl_dbg
command is designed to help you with configuration file design and avoid wasting time attempting
to install with invalid configuration files. With the instl_dbg command you can:
• Parse a client's configuration files for syntax errors.
• Display and set variables, software selections, and use models.
• Detect errors that may occur during a client installation due to faulty configuration files, such
as missing software depots/archives.
After you have developed a new configuration file, run the instl_dbg command from the Ignite-UX
server to ensure that there are no errors in your configuration files. The instl_dbg command first
scans for any syntax errors. Then, instl_dbg substitutes variables, use models, and software
selections (sw_sel) with real values, and writes a single, unified configuration file if the -f option
is specified. Now, you can use this file to install the client. Other options are available for more
thorough checking or to provide more details. For more information, see instl_dbg(1M).
Examples
Enter the following command to debug a client configuration file named system1, print the
debugged configuration file to stdout, and then save the debugged configuration file to a new
file, system1_cfg.out:
instl_dbg -D /var/opt/ignite/clients/system1 -d \
-f system1_cfg.out
To debug this same client configuration file, system1, to show the effects upon the disk layout
when the _hp_disk_layout and _hp_pri_swap values are changed, and then print the "very,
very verbose" (-vvv) output to the console and to the system1_cfg.out file, you would enter
the following command:
instl_dbg -D /var/opt/ignite/clients/system1 -d \
-V _hp_disk_layout="Whole disk (not LVM) with HFS" \
-V _hp_pri_swap=500MB -vvv -f system1_cfg.out
For more information, see instl_dbg(1M).
Using Post-Installation Scripts
You can perform any number of tasks on a client after installing the operating system by providing
a script to be executed. This section provides some common examples to assist you. Additionally,
you can write your own scripts to mount additional disk drives, add additional software, or modify
configurations based on system use.
168 Customizing Your Installation