Ignite-UX Custom Configuration files

"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}=TRUE
Listing the names of cfg clauses in an INDEX file
The following syntax for the manage_index command lists the names of all of the cfg clauses in
an
INDEX file:
manage_index -l -c cfg_clause_name | -r release ] [-o] [-v]
[-i index_filename]
For example:
$ cat INDEX
...
cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
cfg "testing two" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}=TRUE
$ manage_index -l -i /var/tmp/INDEX
testing
testing two
Being able to list the cfg clauses also makes it easier to script Ignite-UX tasks. An example of this
could be a sanity-checking script that ensures all of the configuration files referenced from within
cfg clauses exist and are readable.
6
Such a script might look like:
#!/usr/bin/sh
/opt/ignite/bin/manage_index -l | while read CFG
do
{
eval /opt/ignite/bin/manage_index -w -c \"${CFG}\" | while read FILE
do
if [[ ! -f $FILE ]]
then
print -u2 "Error: file $FILE does not exist"
fi
if [[ ! -r $FILE ]]
then
print -u2 "Error: file $FILE is not readable"
fi
done
}
done
6
Note that this script is a trivial example. The instl_adm command with the –T option would perform these tasks as well as sanity-check the
syntax within the configuration files.
20