"/var/opt/ignite/scripts/multi_plane_graphics"

}

You can also specify multiple conditions. The following example installs a particular piece of previously defined application software if the client is a supported PA-RISC or Itanium-based server or workstation having at least two disks. A message lets you know why it is happening:

( (HARDWARE_MODEL ~ "9000/7.*" MODEL ~ "ia64 .* workstation .*") & (num_disks >= 2) ) { note += "Installed application software contained in apps1."

init sw_sel "apps1" = TRUE

You must use both HARDWARE_MODEL and MODEL because of the differences in the way the uname and model commands work on Itanium-based systems. For example on an Itanium-based client you can use the following commands to find this information:

uname -m

# ia64

model

# ia64 hp workstation zx2000

Notice that the response from the uname command is truncated so it is not possible to determine if the client is a server or a workstation, whereas on a PA-RISC client, the same command results in the following:

uname -m

# 9000/785

model

#9000/785/J6000

Additionally, you can add an else clause so that a choice can be executed automatically. The following example uses a generic variable capability and mathematical expressions to set the primary swap size based on the amount of memory in the client:

(memory > 512Mb) {

init _hp_pri_swap = 512Mb

}

else {

init _hp_pri_swap = memory * 2

}

The preceding examples represent a few of the numerous ways that system attribute keywords can be used in client configurations and must not be considered an exhaustive list.

Customizations based on user selection

One of the ways you can use Ignite-UX to your advantage is to create a customized configuration independent of the client’s hardware setup that can be selected for use repeatedly. For example, you might have some clients that you intend to use as NFS file servers and you would like to be able to quickly install these clients by selecting the same configuration from the GUI.

Let’s assume that you have found NFS file servers to be more efficient if two of their kernel parameters are modified. NFS file servers also require some changes to the /etc/rc.config.d/ nfsconf file using the ch_rc command.

One alternative to effecting these changes manually is to define a custom software selection in /var/opt/ignite/config.local with a sw_sel clause, which then becomes a selection on the Software tab when you are configuring a new client installation. For example, the following clauses would automatically configure your NFS file servers:

sw_source "special configs" { source_format = cmd

}

sw_sel "NFS Server" { sw_category = "Machine Uses" sw_source = "special configs"

Using configuration files 169