Ignite-UX Custom Configuration files

$ manage_index -a -s /var/tmp/script_a -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"
}
scripts {
"/var/tmp/script_a"
}
$ manage_index -t -s /var/tmp/script_a -c "testing" \
> -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"
}
Files (or in this case a script) must exist before they can be removed (or added) with
manage_index. This applies to configuration files as well as scripts.
$ manage_index -a -s /var/tmp/script_a -i /var/tmp/INDEX
ERROR: Cannot read script file: /var/tmp/script_a
ERROR: No read access to file specified by -f
List the names of all configuration files in a cfg clause
The following command enables you to list all the configuration files named in a cfg clause:
manage_index -w -c cfg_clause_name [-v] [-i index_filename]
For example:
$ manage_index -w -c "testing" -i /var/tmp/INDEX
/var/tmp/config_c
/var/tmp/config_a
24