optional post-install scripts

[Peter Stubbs_1]

Hi,

I'd like to allow the installation of different versions of a piece of software to be selected at ignite time.

I have these post install scripts in my config file

post_config_script += "/var/opt/ignite/scripts/install_v1"
post_config_script += "/var/opt/ignite/scripts/install_v1.1"
post_config_script += "/var/opt/ignite/scripts/install_v1.2"
post_config_script += "/var/opt/ignite/scripts/install_v2"

This requires the operator to unselect the versions they don't want to install or else install all versions! ie. They all appear in the "Scripts to be Executed" list in itool and will all run at the post_config stage.

I'd like to have "/var/opt/ignite/scripts/install_v2" as the default but the others as "Available Scripts" so that an operator gets the default one or can choose another.

Does the post_config_script syntax support that or is there some cunning trick I can use to get the same functionality?

[Scot Bean]

Two solutions that I can think of:

1. Combine your four post_config scripts into one big script. Let the script figure out which version to run, based on the target machine.

2. Use Ignite config script logic to determine which one you want to run, and just run the one you want.

(These solutions assume that you can automate the decision to pick one of them.)

You really want to remove the error-prone manual step where an operator has to edit this script list. You may really want ignite to run all by itself (non-interactive), with no operator tending it (i.e. the 'bootsys' cmd).

.....

The only way I know to default to one is to use '=' instead of '+='. But then you get only one of them in the interactive panel. User would have to 'know' the other names and edit them in.

[Simon Lowther · Accepted solution]

a way to do this would be to wrap each command in an in a sw_sel with the source format set to cmd, then setting a default is simply an init sw_sel = true, the operator can select a different script from the software tab in gui
you could also look at the exrequisite statement to make the scripts mutually exclusive

for an example look at language selection in /opt/ignite/data/examples/core11.cfg

[Peter Stubbs_1]

That's a great idea, but when are those scripts executed? If it's before the system's up and running properly I'll need to be pretty careful about using system services (nfs etc)

This is certainly the best idea I've heard though. Thanks!

[Simon Lowther]

the scripts can be executed at various points throughout the install, have a look at pre, post and final commands in instl_adm(4)

[Scott Lindstrom_2]

We just upgraded Ignite (from 3.7 to 4.4) and now our tests seem to show that the post_config_script does not run when we perform disaster recovery testing. Even the Support Center is having trouble with this (they are testing 4.4 and 5.3).

What releases of Ignite do people have in which they know their post_config scripts are actually running?

Here is how we have ours specified:

[/var/opt/ignite]#cat config.local
# /var/opt/ignite/config.local: config file to be used for local customizations.
post_config_script += "/var/opt/ignite/MR_DR_postload.sh"

Scott