Ignite-UX Custom Configuration files

What happens if you
want to create the following extra file systems (for an application)?
/opt/application
/opt/application/static
/var/opt/application
/var/opt/application/data
/var/opt/application/tmp
Ignite-UX has no information about what data might be stored in these file systems because it has
no impacts statements that affect them. Suppose that the impacts are only one level deep and
everything is being tracked against /var and /opt for the application:
impacts = "/opt" 1048576Kb
impacts = "/var " 3673088Kb
If you create those extra file systems, you might easily misjudge their size. Because the impacts
statements have tracked all of the space against /var and /opt, Ignite-UX cannot know how much
space is needed under those file systems so it does not alert you. If your situation is like this, it
would make sense to set up your own Ignite-UX server with the correct impacts keywords rather
than attempting to use installation media.
Assume that the file systems needed for this application are those in Table 5:
Table 5
Mount point File System Size (Mb) Space Used (Mb)
/opt/application/
1024Mb 768Mb
/opt/application/static
512Mb 384Mb
/var/opt/application
2048Mb 1512Mb
/var/opt/application/data
16384Mb 2011Mb
/var/opt/application/tmp
16384Mb 64Mb
Impacts statements for the sw_sel clause associated with this application look like the following:
impacts = "/opt/application" 786432Kb
impacts = "/opt/application/static" 393216Kb
impacts = "/var/opt/application" 1548288Kb
impacts = "/var/opt/application/data" 2059264Kb
impacts = "/var/opt/application/tmp" 65536Kb
The impacts statements place the required impacts at the places where the application (in the
environment in which it is installed) has mount points. With this information, Ignite-UX is aware of
the impacts associated with each file system.
Creating impacts in this manner (for our optional application with only five impacts statements at up
to four levels deep) is a manual job for two reasons:
First, Ignite-UX normally creates impacts at every directory up to the level that you specify. If you
have an archive and you use the archive_impact command to generate the impacts with the
option –l 4, the archive_impact command lists the space used in every directory up to the
fourth level deep. With a large directory structure, this can generate thousands of impacts
117