Ignite-UX Custom Configuration files

$ print "f tmp/a 1024" | /opt/ignite/lbin/gen_impacts
impacts = "tmp" 8Kb
$ print "f tmp/a 10240" | /opt/ignite/lbin/gen_impacts
impacts = "tmp" 16Kb
The first command specifies a file size tmp/a of 1KB, but the impact is 8KB. The second command
specifies a file size of tmp/a as 10KB, and the impact is 16KB.
Most systems these days use VxFS instead of HFS for file systems. VxFS file systems are extent-
based file systems and can usually allocate (space allowing) blocks as small as 1KB to a file.
When you have the impacts for a HFS file system applied to a VxFS file system, the size
requirements can be significantly overstated because of the assumptions that gen_impacts
58
makes.
The gen_impacts command assumes that all files are located on HFS file systems and have an
8KB fragment size and a 64KB block size. The gen_impacts command gets the approximate
size correct when the file is large enough to use indirect block to track the space used by the file.
These overstated impacts are not considered wrong, just conservative. Ignite-UX cannot predict
when impacts are being generated or what kind of file system on which the software is installed.
The correct approach is to take the conservative approach.
Lastly, consider the following example of what effect different fragment sizes have on the impacts
generated for a depot containing a copy of the B.11.11 Version Mission Critical (MC) Operating
Environment (OE) with the default fragment size (8KB), a 2KB fragment size, and a 1KB fragment
size:
# /usr/sbin/swlist -l file -d -a type -a name -a size @/depot/11iv1_mc/core |
awk ' $3 == "f" || $3 == "d" { printf("%s %s %s\n", $3, $2, $4) } ' |
/opt/ignite/lbin/gen_impacts -l 2 -f 1024
impacts = "/" 1138Kb
impacts = "/usr/lib" 599090Kb
impacts = "/sbin/lib" 561Kb
impacts = "/usr/conf" 107843Kb
impacts = "/sbin/init.d" 664Kb
…
# /usr/sbin/swlist -l file -d -a type -a name -a size @/ depot/11iv1_mc/core|
awk ' $3 == "f" || $3 == "d" { printf("%s %s %s\n", $3, $2, $4) } ' |
/opt/ignite/lbin/gen_impacts -l 2 -f 2048
impacts = "/" 1138Kb
impacts = "/usr/lib" 603124Kb
impacts = "/sbin/lib" 578Kb
impacts = "/usr/conf" 108359Kb
impacts = "/sbin/init.d" 734Kb
…
# /usr/sbin/swlist -l file -d -a type -a name -a size @/depot/11iv1_mc/core |
awk ' $3 == "f" || $3 == "d" { printf("%s %s %s\n", $3, $2, $4) } ' |
/opt/ignite/lbin/gen_impacts -l 2 –f 8192
impacts = "/" 1138Kb
impacts = "/usr/lib" 632140Kb
impacts = "/sbin/lib" 684Kb
impacts = "/usr/conf" 111703Kb
58
The archive_impact and make_arch_config commands both call gen_impacts to generate impacts statements.
96