Ignite-UX (IUX) Frequently Asked Questions (July 2013)

or both of the clients.
=============================================================================
==
2.3
Q: How can I set the timezone for messages during the install?
A: The HP-UX install kernel defaults to eastern US timezone. If you
would like the log messages to come out in some other timezone, you
can set the "TZ" environment variable within the *INSTALLFS files
using instl_adm. Doing this will not impact the very first message
that Ignite-UX produces, but it will take effect as soon as Ignite
processes that variable setting. For example, to set TZ to mountain
timezone:
# instl_adm -d > /tmp/installfs.out
# echo 'env_vars += "TZ=MST7MDT"' >> /tmp/installfs.out
# instl_adm -f /tmp/installfs.out
Note: The "timezone" keyword in the Ignite-UX config file determines
what timezone is actually applied to the system after the
installation is complete. Setting the TZ env variable as shown above
is only used during the installation. (See instl_adm(4) for the
"timezone" keyword).
=============================================================================
==
----------------------------------------
3. Configuration Files
----------------------------------------
3.1
Q: What should go in which configuration file? Also, what should go in
INSTALLFS?
A: Here is a short description of the common uses of the various
configurations. Obviously, there can be situations that are not
"common" and variations will occur:
- INSTALLFS (accessed/modified via instl_adm(1M)) - Information that
is needed at boot, such as GUI controls and networking.
- /var/opt/ignite/config.local - Information that should be globally
applied to all clients and defines the post_[load/config]_scripts
run on all clients.
- /opt/ignite/data/Rel_<release>/config - This file sets the
definitions for that release and should not be modified.
- /var/opt/ignite/date/Rel_<release>/*_cfg - Information regarding
software selections/sources. These files should be created by
make_config (run against an Software Distributor depot) or in the
archive case, edited versions of the examples in
/opt/ignite/data/examples/[core|noncore].cfg.
When Ignite-UX is run for a client, all of these configuration files