User's Guide
Once a relea
se identifier has been determined for the configuration file, the manage_index
command behaves as though it was given that release identifier with the –r option.
5
In the following example, if you subsequently tried to add a configuration file based upon a
release, it would not work because none of the configuration files contains an operating system
release in their path names. However, you can add a file based upon a release if you first add the
expected information in the path.
$ cat INDEX
cfg "testing" {
description "testing clause"
}
$ touch config_a config_b
$ print "release=B.11.11" > config_c
$ manage_index -a -f /var/tmp/config_c -c "testing" \
> -i /var/tmp/INDEX
$ cat INDEX
...
cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
}
The following example adds the configuration file /opt/ignite/data/Rel_B.11.11/config
to the cfg clause that then enables you to add the configuration file /var/tmp/config_a.
manage_index -a -f /opt/ignite/data/Rel_B.11.11/config -c "testing" \
> -i /var/tmp/INDEX
$ manage_index -a -f /var/tmp/config_a -r B.11.11 \
> -i /var/tmp/INDEX
$ cat INDEX
...
cfg "testing" {
description "testing clause"
"/var/tmp/config_c"
"/opt/ignite/data/Rel_B.11.11/config"
"/var/tmp/config_a"
}
Adding scripts to the INDEX file
As part of the syntax for configuration index files, there is a keyword called scripts, which
enables you to define user-selectable scripts that can be run during installation and recovery:
manage_index -a -s script
_file_name [-p] [-v] [-i index_filename]
The manage_index command with the –a and –s options allows you to add scripts into an
INDEX file. For example:
$ manage_index -a -s /var/tmp/script_a \
> -i /var/tmp/INDEX
$ cat INDEX
…
5
This information is applicable to all forms of the manage_index command that need to search for or match release identifiers.
17