Configuration files and INDEX files
This section discusses the contents of configuration files and INDEX files to help you understand the purpose of the files, not to document what is occurring in the files.
The INDEX fileThe file /var/opt/ignite/INDEX is used during
$ pwd /var/opt/ignite $ cat INDEX
#/var/opt/ignite/INDEX
#This file is used to define the
#and to define which config files are associated with each
#configuration. See the ignite(5), instl_adm(4), and
#manage_index(1M) man pages for details.
#
#NOTE: The manage_index command is used to maintain this file.
#Comments, logic expressions and formatting changes are not
#preserved by manage_index.
#
#WARNING: User comments (lines beginning with '#' ), and any user
#formatting in the body of this file are _not_ preserved
#when the version of
#
cfg
description "This selection supplies the default system configuration that HP supplies for the B.11.11 release."
"/opt/ignite/data/Rel_B.11.11/config" "/opt/ignite/data/Rel_B.11.11/hw_patches_cfg" "/var/opt/ignite/config.local"
}
If the cfg clause in the INDEX file were to be the default cfg clause (in a
cfg
description "This selection supplies the default system configuration that HP supplies for the B.11.11 release."
"/opt/ignite/data/Rel_B.11.11/config" "/opt/ignite/data/Rel_B.11.11/hw_patches_cfg" "/var/opt/ignite/config.local"
}=TRUE
Of course, the INDEX file is never to be edited manually; instead, the manage_index command should be used to maintain this file. The actual command needed to set a cfg clause to be the default clause is as follows:
# manage_index
The manage_index command operates on the /var/opt/ignite/INDEX file by default, so the INDEX file does not need to be specified on the command line.
9