Ignite-UX Custom Configuration files

scripts {
"/var/tmp/script_a"
}
On the Advanced tab in the Ignite-UX GUI, the sample script appears so it can be selected and
run by a user. The scripts clause in the INDEX file is global in scope; scripts defined here are
available for selection with any cfg clause in the INDEX file. You should be careful not to define
scripts that make assumptions about the release they will be run on or are not portable across all
HP-UX releases.
Removing cfg clauses from an INDEX file
The –d option is used to remove cfg clauses from an INDEX file using manage_index:
manage_index -d -c cfg_clause_name | -r release [-p] [-v]
[-i index_filename]
The following example removes the cfg clause "testing two" from the INDEX file completely:
$ 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"
}
$ manage_index -d -c "testing two" -i /var/tmp/test/INDEX
You can see that the cfg clause "testing two" has been removed from the INDEX file:
$ cat INDEX...
cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
The –r option operates on all cfg clauses applicable to a release identifier. If you reference cfg
clauses by release, you need to be careful. In the following example, both cfg clauses have a
release identifier that matches B.11.11, so both are removed from the INDEX file.
$ cat INDEX.save
...
cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
18