User's Guide

This r
uns the itool user interface as though it were running on the client system.
15
You must run
itool as root.
Important:
Do not change time-related information in the Ignite-UX GUI unless the
system
you are on is considered non-production; altering the time
information changes the system clock.
Configuration changes are saved into the configuration file in the per-client directory.
When exiting itool, there is no need for concern with respect to the list of options it presents; no
action should be taken for any of them. The different options set a different return code from
itool. The return code is how itool communicates the next action to the program that calls it
when it is running during a normal installation or recovery.
Combining instl_dbg and itool
If a configuration file (a file named config) exists in the client directory, its configuration
information is used (for example, which cfg clause) instead of the default. This is the reason the
itool program was discussed in the previous section.
When you use itool to change configurations and then run instl_dbg to see what is
happening in the configurations, it makes it possible to test configurations and changes without
having to boot a system and attempt to install the system.
Running instl_dbg in this way enables you to see the configuration the way Ignite-UX parses it
on that client.
Running instl_dbg
You can use instl_dbg to test some aspects of your configuration; for instance, with the –c
option you can perform system configuration sanity checks. In the following example, it is assumed
that you have changed working directories to a per-client directory on an Ignite-UX server
(/var/opt/ignite/clients/<MAC>).
# instl_dbg -D . -c
======= System Configuration Checks ======
WARNING: The disk at: 0/8/0/0.2.0 (SEAGATE_ST39173WC) appears to contain a
file
system and boot area. Continuing the installation will destroy any
existing data on this disk.
The –c option allows you to see configuration check messages that would normally only be seen
during an installation or recovery session. This allows you to preview what you will see during an
installation or recovery session.
15
When an installation is controlled from the server, itool is actually run on the server. However, it is run with the –m
push option since configuration changes are pushed to the client system.
36