ignite-ux post_config question

[Albert Kwok_2]

When I ignite a new server, it executed "post_config_script" before it loaded the "post_config_cmd software". Is there a way to reverse this order? Thanks

[Steven E. Protter]

The order of events can be manipulated in Ignite in the INDEX file.

/var/opt/ignite/INDEX

Snippet:

cfg "HP-UX B.11.11 Image Hebron" {
description "This is a golden image built on tzfat.juf.net HP-UXB.11.11
release."
"/opt/ignite/data/Rel_B.11.11/config"
"/opt/ignite/data/Rel_B.11.11/hw_patches_cfg"
"/var/opt/ignite/data/Rel_B.11.11/core11_image_arch.cfg"
"/var/opt/ignite/recovery/config.local.hebron"
"/var/opt/ignite/saved_cfgs/HP-UX_B.11.11_Image_Hebron"
}


You can't do the Core OS before the local configuration, but you can do a lot.

Perhaps you can post up a little more detail, such as Ignite Version, OS version. etc.

I think by default post_config_cmd software is supposed to be befoer post_config_script.

SEP

[Albert Kwok_2]

We are running Ignite version B.4.3.91 on 11.11. Generally, I would think that the "post_config_cmd software" would be installed before the "post_config_script". However, I was reading my install.log file and found out our Ignite would run the "post_config_script" prior to the "post_config_cmd software".

[Steven E. Protter]

I you have the time to do the isntallation without the post install script, everything should be all right.

The post install script can be run in the config.hebron file I posted above or standalone after the installation.

I'm guessing that some configuration file has its lines crossed.

You can check it with instl_adm -T

Correct any errors that occur.

You might if frustrated try dropping the client and adding it in again as well.

There are so many places in Ignite for something to go wrong, it can be like searching for a needle in a haystack(technical term!).

SEP