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

configuration:
mod_kernel += "swchunk 4096"
With swchunk set to 4096, you are able to utilize up to 64 GB of
swap, assuming that Ignite-UX had to set maxswapchunks to its maximum
value of 16384.
Note: Ignite-UX does not detect any changes you make to swchunk, it
limits the total size of all swap space to 32 GB.
To calculate how much swap can be utilized you multiply swchunk by
maxswapchunks, for example:
16384 * 4096 = 67108864
Since swchunk is measured in KB 67108864 / (1024*1024) = 64 GB.
Ignite-UX lets you configure more space in swap space than what the
kernel can use so getting swchunk and maxswapchunks set correctly for
a large configuration is important.
Currently the maximum supported value of swchunk is 16384. This
gives a total of 256 GB of addressable swap with both swchunk and
maxswapchunks set to 16384.
Try not to over configure the amount of swap that can be addressed
when setting values for maxswapchunks and swchunk. These values are
used to allocate kernel memory that is used to keep track of swap
resources, setting them too large wastes memory. To efficiently use
kernel memory keep swchunk as a power of 2 (for example: 2048, 4096,
8192, 16384, etc.).
When choosing values try to keep swchunk to the lowest value that you
can, and then choose the value needed for maxswapchunks to address
the swap needed. On a system that actively swaps memory to a swap
space there may be performance implications when increasing swchunk
past its default of 2048.
The HP-UX Memory Management White Paper (mem_mgt.txt located in
/usr/share/doc) contains detailed information about how swap is
controlled inside the kernel.
Additionally, to create logical volumes as unused logical volumes
rather than swap logical volumes you can configure them to be used
for swap after the installation process has completed. This is only
important if you need the swap spaces allocated in a particular
order.
=============================================================================
==
5.10
Q: Why do the text fields in the Ignite-UX TUI not accept my input, and the
dialogs re-open or loop?
A: The text fields within the Ignite-UX TUI do not recognize keyboard
input when the "Insert" key is active. Make sure that the the