Ignite-UX Custom Configuration files

cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
"/var/tmp/config_a"
}=TRUE
cfg "old testing two" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
In the previous example, you removed a specific configuration file from the cfg clause
“testing”. The following example removes config_c from all B.11.11 clauses:
$ manage_index -t -f /var/tmp/config_c -r B.11.11 \
> -i /var/tmp/INDEX
$ cat INDEX
...
cfg "testing two" {
description "testing clause"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
"/var/tmp/config_a"
}=TRUE
cfg "old testing two" {
description "testing clause"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
The cfg clause "testing" is not modified in this example. Earlier in the section Adding a
configuration file to a clause or "release" on page 6, we discussed how manage_index associates
a release identifier with a cfg c
lause. The configuration files associated with the cfg clause
“testing” no longer meets any of the conditions that allows manage_index to determine a
release identifier. Since no release identifier could be determined, the configuration file
/var/tmp/config_c was not removed from the cfg clause.
Important:
A cfg clause must have a release keyword in one
of the configuration
files associated with it.
Removing a script from an INDEX file
Earlier you learned how to add a script into the configuration so that it appears on the Advanced
tab in the Ignite-UX GUI. You use the following form of the command to remove the script:
manage_index -t -s script
_file_name [-p] [-v] [-i index_filename]
The following example adds a script and then removes it:
23