HP-UX Workload Manager A.03.02.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

HP-UX Workload Manager Release Notes

Known problems and workarounds

WLM configurations cannot be activated with fewer than 100 Mbytes

of memory available

Issue When controlling memory, WLM allocates at least a minimum amount to

each group. If extended_shares is enabled, this minimum is 0.2% of the

available memory; otherwise, it is 1%. (Available memory is the amount

reported by prmavail; it is the amount that is not reserved for the kernel

(/stand/vmunix) and its data structures and for nonkernel system processes.

Thus, available memory is not the total memory on the system. Available

memory varies over time. For more information, see the Process Resource

Manager User’s Guide, available in /opt/prm/doc.) WLM requires that this

minimum represent at least 1 Mbyte of memory. Thus, when memory

control is used, the system should have at least 100 Mbytes of available

memory, or at least 500 Mbytes if extended_shares is enabled.

Workaround Increase the system’s memory or decrease the minimum dynamic buffer

cache using the kernel parameter dbc_min_pct.

Secure Resource Partitions:

Blocked port on a virtual network interface

Issue Using the HP-UX feature Security Containment, you can set up a virtual

network interface for each secure compartment. A process in one secure

compartment can bind to a socket on a virtual network interface associated

with a different secure compartment. Although this process will not be able

to accept connections or use the socket to send or receive data, it does

prevent other processes from binding to that socket.

Workaround Be sure your applications that access the network bind only to sockets on

the virtual network interface created for their respective secure

compartments. Fore more information, see the following documents:

For more information, refer to the Security Containment release notes and

the HP-UX 11i Security Containment Administrator’s Guide.

Reaching the system V semaphore limit

Issue If your system has many system V semaphores in use, WLM usage of

semaphores may push the total number of semaphores over system

limits—especially if the WLM configuration contains a large number of data

collectors. The WLM daemon wlmd creates two semaphore sets: one

containing a single semaphore; the other containing a semaphore for each

data collector in the WLM configuration.