Ignite-UX can make intelligent decisions about
installation parameters when it runs, based on information it reads
from the client. Instead of forcing static values (for example, swap
size or kernel parameters), Ignite-UX can determine the best values
for these based on the characteristics of the client.
This feature can make the configurations that
you set up more general purpose and limit the need for multiple, custom
configurations to handle minor system differences.
These decisions are specified in a C-like language
and grammar unique to Ignite-UX. For more information, see instl_adm(1M).
The following examples show how Ignite-UX set
installation parameters dynamically.
Example 1
In this example, if the client’s root disk
is smaller than 8.5 GB and has less than 1 GB (1024 MB) of random
access memory (RAM), then the primary swap partition size (_hp_pri_swap) is set to 512 MB; otherwise, it is set to 1
GB. If the disk is larger than 8.5 GB, then _hp_pri_swap is set to 1024 MB or 4096 MB, depending on the memory size.
Add the following lines to the end of the file /var/opt/ignite/config.local as this file is typically
referenced in all configurations defined in the /var/opt/ignite/INDEX file:
# default to very minimal swap of 8500MB
# unless the disk is larger than 8.5 GB
# and we have more than 512MB RAM
(disk[_hp_root_disk].size < 8500MB)
{
(memory < 1024Mb) {
init _hp_pri_swap=512MB
} else {
init _hp_pri_swap=1024MB
}
} else {
(memory < 2048Mb) {
init _hp_pri_swap=1024MB
} else {
init _hp_pri_swap=4096MB
}
} |
You could also put this in a separate file, for
example, /var/opt/ignite/data/Rel_B.11.11/custom_cfg, and then add that file name to the desired cfg clause in the /var/opt/ignite/INDEX file.
Additionally, you could add this to the configuration
file created for automatic installations. If the _hp_pri_swap parameter is set later in the order of files searched in the cfg
clause, this setting is overwritten. The configuration file parsing
order and precedence is documented in instl_adm(4) and
in “Using Configuration Files”.
 |
| |
|
 | CAUTION: The per-client configuration file in /var/opt/ignite/clients/client used for noninteractive installations is overwritten as part of
the installation process. |
|
| |
|
Example 2
To force the installation of a patch bundle if
the client matches a regular expression, such as a hardware architecture
type like J6700 or J6750 PA-RISC workstations, add the following lines
to the end of the /var/opt/ignite/data/Rel_B.11.11/custom_cfg configuration file:
# check for H/W model J6700 or J6750
# and add the Misc_Patches bundle if true
(hardware_model ~ "9000/785/J67[05]0") {init sw_sel "Misc_Patches" = true} |
Example 3
In this example, Ignite-UX runs a previously created
post-installation script and increases a tunable kernel parameter
if it determines the client is a C3600, C3650, C3700, or C3750 workstation.
If not, it sets a default value for the kernel parameter:
post_config_script += "/var/opt/ignite/scripts/new_C_series_special"
(HARDWARE_MODEL == "9000/785/C3[67][05]0") { mod_kernel += "maxuprc 300"
} else {mod_kernel += "maxuprc 100"} |
Example 4
You can specify an entirely different custom configuration
based on the size of the client’s RAM and disk size. To set
the default configuration dynamically to put into effect, it must
go into the [W|V|I]INSTALLFS file using instl_adm(1M) as in the following script excerpt:
# For a system with only one disk and small memory, select
# the "small system configuration"
(num_disks == 1 & memory < 256MB )
{cfg "small system configuration" = true} |
Checking Modified Files for Errors |
|
You can validate the syntax of a file that is not yet in the /var/opt/ignite/INDEX file to avoid installation problems later, by entering the following:
instl_adm -T -f file
After you modify configuration files, always validate the syntax of all of the files that are
referenced in the cfg clauses in the /var/opt/ignite/INDEX file, by entering the following:
instl_adm -T
Printable version
