|
|
|
maxfiles_lim(5) -- hard maximum number of file descriptors per process
|
|
maxfiles_lim specifies the system hard limit for the number of file descriptors that a process is allowed to have for open files at any given time. It is possible for a nonsuperuser process to increase its soft limit up to this hard limit. Who Is Expected to Change This Tunable? Anyone expecting to run applications using large numbers of file descriptors. |
|
maxrsessiz(5) -- maximum size (in bytes) of the RSE
|
|
Itanium-based systems utilize a per-process register stack in main memory (for more information see the Intel IA-64 Architecture Software Developer's Manual, Volume 2, Chapter 6). This stack moves registers between the physical registers and main memory and is maintained by the Register Stack Engine (RSE). maxrsessiz determines the size of this stack. Who is Expected to Change This Tunable? Anyon... |
|
|
maxrsessiz_64bit(5) -- maximum size (in bytes) of the RSE
|
|
Itanium-based systems utilize a per-process register stack in main memory (for more information see the Intel IA-64 Architecture Software Developer's Manual, Volume 2, Chapter 6). This stack moves registers between the physical registers and main memory and is maintained by the Register Stack Engine (RSE). maxrsessiz determines the size of this stack. Who is Expected to Change This Tunable? Anyon... |
|
maxssiz(5) -- maximum size (in bytes) of the stack for any user process
|
|
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. Each segment occupies an architecturally defined range of the virtual address space which sets the upper limit to their size. However, text, data and stack segments may have a smaller maximum enforced via the maxtsiz, maxdsiz and maxssiz tunables. maxssiz and maxss... |
|
maxssiz_64bit(5) -- maximum size (in bytes) of the stack for any user process
|
|
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. Each segment occupies an architecturally defined range of the virtual address space which sets the upper limit to their size. However, text, data and stack segments may have a smaller maximum enforced via the maxtsiz, maxdsiz and maxssiz tunables. maxssiz and maxss... |
|
maxtsiz(5) -- maximum size (in bytes) of the text segment for any user process
|
|
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. Each segment occupies an architecturally defined range of the virtual address space which sets the upper limit to their size, but text, data and stack segments may have a smaller maximum enforced via the maxtsiz, maxdsiz and maxssiz tunables. maxtsiz controls the s... |
|
maxtsiz_64bit(5) -- maximum size (in bytes) of the text segment for any user process
|
|
User programs on HP-UX systems are composed of five discrete segments of virtual memory: text (or code), data, stack, shared, and I/O. Each segment occupies an architecturally defined range of the virtual address space which sets the upper limit to their size, but text, data and stack segments may have a smaller maximum enforced via the maxtsiz, maxdsiz and maxssiz tunables. maxtsiz controls the s... |
|
maxuprc(5) -- limits the maximum number of concurrent user processes per user
|
|
maxuprc is a dynamic tunable that limits the maximum number of processes per user. Only root can have more than the number of processes limited by maxuprc. Who is Expected to Change This Tunable? System administrators can change the value of maxuprc depending on the usage of the system. |
|
maxusers(5) -- OBSOLETED
|
|
This tunable has been obsoleted and removed in the HP-UX 11i Version 2 release. Please do not make any changes to this tunable as they will have no effect on the kernel. Prior to the HP-UX 11i Version 2 release, the maxusers tunable was used to calculate the default values of nclist, nfile, and ninode, all of which control kernel data structures that determine the system resource allocation. As of... |
|
maxvgs(5) -- maximum number of LVM Volume Groups that can be created/activated on the system
|
|
Maximum number of LVM Volume Groups which may be created or activated on the system. This value also limits the range of Volume Group numbers allowed. A maxvgs value of 10, for example, allows 10 Volume Groups to be created on the system, and the Volume Group number of each Volume Group is a unique value in the range of 0 to 9. Who Is Expected to Change This Tunable? Anyone. |
|
max_acct_file_size(5) -- defines the maximum accounting file size
|
|
max_acct_file_size is a dynamic tunable that limits the maximum accounting file size. See acct(2) and acct(4). If max_acct_file_size was set to a value that is not a multiple of the accounting record size, the tunable will be rounded up to the next full record silently unless the maximum limit is reached. In this case, the tunable will be rounded down to the nearest full record silently. The only ... |
|
max_async_ports(5) -- maximum number of asynchronous disk ports that can be open at any time
|
|
The asynchronous disk driver provides an interface to execute highperformance I/O to the raw disk. Instead of reading or writing directly to the raw disk, a process writes requests to the asynchronous driver which then makes appropriate calls to the disk driver. Every process that opens the asynchronous disk driver is assigned a port. The driver uses the port to keep track of I/O and other interna... |
|
max_mem_window(5) -- maximum number of group-private 32-bit shared memory configurable by users
|
|
32-bit processes usually share the global quadrants 3 and 4 for such things as I/O mappings, shared libraries, shared mapped files, etc. However, you may wish to use quadrant 3 in a more limited sharing fashion with only a select group of processes. Memory windows allow this functionality. If this tunable is set to 0, 32-bit programs always use the global Q3 and Q4 for shared memory. If this tunab... |
|
max_thread_proc(5) -- defines the maximum number of concurrent threads allowed per process.
|
|
max_thread_proc is a dynamic tunable that limits the maximum number of threads allowed per process on the system. When tuning max_thread_proc, the maximum number of threads allowed per process will be the new value of max_thread_proc. No process will be able to create new threads such that the total count of its threads exceeds max_thread_proc. Who is Expected to Change This Tunable? System admini... |
|
mesg(5) -- enable or disable System V IPC messages at boot time
|
|
The mesg tunable is obsolete. The System V IPC message subsystem is always enabled. |
