Ignite-UX Custom Configuration files

Creating a new cfg clause from an existing clause
Using the following form of manage_index, you can easily to create a new cfg clause from an
existing clause:
manage_index -n existing_clause_name -c new_clause_name [-p] [-v]
[-i index_filename]
For example:
$ manage_index -n "testing" -c "old testing two" -i /var/tmp/INDEX
$ manage_index -l -i /var/tmp/INDEX
testing two
testing
old testing two
Removing a configuration file from a cfg clause
Earlier you learned how to add a configuration file to a clause. Now you can do the opposite,
which is to remove configuration files from cfg clauses:
manage_index -t -f config_file_name [-c cfg_clause_name| -r release]
[-p] [-v] [-i
index_filename]
In the following example, a configuration file is removed from a cfg clause and then, a file is
removed from all of the cfg clauses for one release:
$ cat INDEX
...
cfg "testing two" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/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"
}
$ manage_index -t -f "/opt/ignite/data/Rel_B.11.11/config" -c "testing" \
> -i /var/tmp/INDEX
$ cat INDEX
...
cfg "testing two" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
22