Designing a config file to meet your needs can be a very tedious
task. It usually requires a lot of trial and error. Beginning with
Ignite-UX version A/B 2.2.4 (May 2000), the instl_dbg command is available to help you with config file design.
With the instl_dbg command you can:
Parse a client's configuration files
for syntax errors.
Place all relevant configuration information into
one file for review.
Display and set variables, software selections,
and use models.
Detect any other 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 config file, run instl_dbg from the Ignite-UX server to parse the specified client's
config file as well as any of the server's configuration files referenced
by the client's config file. instl_dbg first scans for any syntax errors. After syntax is checked, instl_dbg substitutes variables, use models, and software selections (sw_sel) with real values, and writes a single, unified
config file if the -f option is specified. You can then compare this
file with your original to determine required changes, or use this
file as is to install the client. More options are available for
more thorough checking or to provide more detail.
Example uses
To debug a client system1 config file and print the debugged
config file to stdout and save the debugged config file to system1_cfg.out:
instl_dbg -D /var/opt/ignite/clients/system1 -d -f system1_cfg.out
Debug the config file for the client named system1, show the
effects upon the disk layout when the value of _hp_disk_layout and _hp_pri_swap are changed, and print the "very, very verbose"
(-vvv) output to the screen as well as the verbose output to system1_cfg.out:
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
Additional examples can be found in the instl_dbg(1M) manpage.
Printable version
