Ignite-UX Reference (March 2010, B3921-90005)

instl_dbg(1M) instl_dbg(1M)
NAME
instl_dbg − parse and debug an Ignite-UX client’s configuration files
SYNOPSIS
/opt/ignite/bin/instl_dbg -D client_directory [-f file][-v][-a {l|r}]
[-cdlsh|-A][-V var[=value]] [-S swsel[=TRUE|=FALSE]]
[-U use_model[=TRUE|=FALSE]] [-n][-?]
DESCRIPTION
instl_dbg is used to parse a client’s configuration files for syntax errors, place all relevant configuration
information into one file, display/set variables, software selections, and use models, and detect any other
errors that may occur during the execution of an installation due to faulty configuration files.
The instl_dbg command should be executed on the Ignite server. The directory given in the -D
option must point to a client directory usually located in /var/opt/ignite/clients. (See
add_new_client(1m) for more information about adding Ignite-UX clients.) The client directory must con-
tain io.info, hw.info, host.info, and config.sys. It may optionally contain a config
file. (For more information about these files see instl_adm(4).)
instl_dbg will parse the specified client’s configuration files as well as any of the server’s configuration
files that may be referenced by the client’s configuration files. It will first scan for any syntax errors. If any
are found, execution is halted, and an error is reported. After the syntax is checked, substitutions for vari-
ables, use models, and software selections (sw_sel) will occur. Finally, a single, unified configuration file
will be written (if the -f option is specified). More options may be given so that instl_dbg will per-
form more thorough checking or provide more detail.
Options
instl_dbg recognizes the following options:
-D client_directory
Specifies the location of the client’s configuration files.
-f file Specifies the file to which instl_dbg will write the final configuration. To
write the configuration file to stdout, use - for file. If no filename is given,
instl_dbg will not produce an output file. All logic expressions are evalu-
ated in the file, thus making it easier to determine what the end result will be.
-v Instructs instl_dbg to produce more verbose output in the configuration
file. Verbose output includes configuration index definitions, sw_sel definitions,
and software category definitions. To display verbose information such as the
state of a variable, sw_sels, or use model before and after command line sub-
stitution the "very, very verbose" option may be used. Replace the -v option
with the -vvv option. The -vvv option implies the -v option.
-a {l|r} Instructs instl_dbg to perform access checks for all selected sw_sels. An
access check verifies that the remote server may be reached and the specified
software may be retrieved. The tests attempt to retrieve the sw_sel in a simi-
lar manner as the actual installation does. The tests may be performed on the
local server when l (ell) follows this option, or they may be run on the remote
client system when r follows this option. The tests will only be performed on
the client system if it may be logged into with the remsh command. Note that
when tests are performed from the server, the tests cannot always tell if the
client will be able to access a sw_sel.
-c Instructs instl_dbg to execute system configuration (sanity) checks and dis-
play the results to stdout.
-d Instructs instl_dbg to display the disk and file system layout details to std-
out.
1