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

ignite(5) ignite(5)
• Replace or repair the failed hardware.
• Go to the client console and perform a network boot from the server on which the archive
resides, or perform a boot from the tape.
• If the client cannot boot over the network or is on a different subnet than the Ignite-UX server,
see make_boot_tape(1M).
• After the client is booted, select your recovery archive from the list of configuration choices dis-
played for installation on your client.
• Ignite-UX detects from the configuration file for the archive that this is a recovery situation and
uses the archive for recovery rather than for install.
Note that recovery archive creation using the Ignite-UX user interface requires a graphical display. A
recovery archive cannot be created by a server running in ASCII mode. Once created, however, the recov-
ery archive may be installed on the client using the ASCII interface on either the client or the server.
Note that although permissible within HP-UX, using characters that do not have a printable graphic that are
likely to confuse the terminal on the hardware you commonly use is not recommended. Filenames with
these characters cause warning messages to be displayed by make_tape_recovery or
make_net_recovery. In addition, files that contain these non-printable characters are not included in
the archive.
International Code Set Support
Ignite-UX uses a variety of system commands to accomplish its functionality. Because the output of many
of these commands is parsed, Ignite-UX ensures that the POSIX locale is normally used by modifying envi-
ronment variables. Help text and some command output not parsed by Ignite-UX will be left in the user’s
specified locale.
EXTERNAL INPUTS AND INFLUENCES
Default Options
The server maintains a defaults file, ignite.defs, located at
/var/opt/ignite/server/ignite.defs. This file contains a subset of the values that are
entered on the Server Configuration screen.
The following values and their defaults are shipped in the Ignite-UX product:
client_timeout: 30
Time (in mins) until the client is declared hung.
halt_when_done: false
Halt the client after installation rather than reboot to invoke set_parms.
ignite_welcome: true
Show the server’s welcome screen.
itool_welcome: true
Ask for customer information during client installation.
new_client_notification: true
Asks whether the user should be notified when new clients boot.
print_enhanced_manifest: false
Print the manifest using HP-PCL3 control codes for an enhanced output.
full_recovery_info: true
Show all the information screens about recovery archive creation.
Locking
In order to allow multiple install sessions to run concurrently with the currently installing process, ignite
will lock a client during a New Install or a Repeat Install. This lock is tested in the actions: "New Install",
"Repeat Installation", "Stop Client" and "Remove Client".
The lock is removed when the client is stopped or COMPLETE. For stopped clients, it is possible for
10