impacts = "/sbin/init.d" 1256Kb

…

The size differences in the first four impacts are summarized in Table 4 (the percentage difference is between the 2KB and 8KB fragments compared to the 1KB fragment impacts):

Table 4

Impacts

Size (1KB)

Size(2KB)

% difference

Size (8KB)

%difference

 

 

 

 

 

 

/

1138

1138

0.0%

1138

0.0%

/usr/lib

599090

603124

0.7%

632140

5.5%

/sbin/lib

561

578

3.0%

684

21.9%

/usr/conf

107843

108359

0.5%

111703

3.6%

/sbin/init.d

664

743

11.9%

1256

89.2%

The percentage increases are somewhat variable but when more space is used for the larger impacts, the larger the fragment size. The impacts are made much larger when a directory structure contains many very small files.

The reason why "/" is the same size is that gen_impacts allocates 1KB to an impact level whenever it sees a directory mentioned. The "/" directory in this case appears 1138 times in the swlist output (so multiple mentions of a directory in the output from swlist can also bloat impacts).

Caution:

If you change or somehow recalculate impacts in any way, you must be very careful. Impacts that do not fully take into account the software impacts to a system may lead to configurations that cannot install a system (because of file system full problems).

Another issue that may cause overstated impacts is hard links. Before Ignite-UX version C.6.4 Ignite- UX would assume that every file that was to be installed from an archive (this includes recovery archives) would occupy the same amount of space as its size ignoring the link count. The space contributed by hard linked files will not be counted multiple times (once for each link) from Ignite-UX version C.6.4 onwards. If you have upgraded an Ignite server from a version prior to C.6.4 you might consider regenerating impacts for golden images.

_hp_custom_sys

The _hp_custom_sys string variable is used in conditional statements surrounding network and system identity information when the Ignite-UX GUI writes out a configuration file. This variable can be used in conditionals in configuration files to define multiple sets of network parameters that can be selected from the Additional screen. You can see how this variable is used by clicking the Save As button during an installation after modifying the parameters under the System tab and looking at the resulting file in the /var/opt/ignite/saved_cfgs directory.

Never use the _hp_custom_sys variable in custom configurations. Ignite-UX uses this variable in the configuration files it can produce so setting it's value outside of those files may interfere with it's use by Ignite-UX.

97