|
|
|
limits(5) -- implementation-specific constants
|
|
The following symbols are defined in and are used throughout the descriptive text of this manual. The column headed HP-UX Value lists the values that application writers should assume for portability across all HP-UX systems. Symbols after values are interpreted as follows: + Actual limit might be greater than specified value on certain HP-UX systems. - Actual limit might be less than t... |
|
man(5) -- macros for formatting manpages
|
|
The man macros are used by the man and nroff commands (see man(1) and nroff(1)) - and are usable by troff (see third-party documentation) - to format the on-line versions of manpages found in HP-UX Reference and other related reference manuals. The man command calls nroff. man and nroff Defaults The default page size is 85 characters by 66 lines (8.5x11 inches), with a 75-character by 60-line text... |
|
|
manuals(5) -- list of HP-UX documentation
|
|
The latest HP-UX user manuals and white papers are available at: http://www.docs.hp.com. Hewlett-Packard Company - 1 - HP-UX 11i Version 2: August 2003 |
|
math(5) -- math functions, constants, and types
|
|
This file contains declarations of all the functions in the Math Library (described in Section (3M)). For Itanium(R)-based systems, included in a compilation under the -fpwidetypes option, this file defines the types extended The Itanium-based 80-bit double-extended type. quad An IEEE 754-compliant, 128-bit floating-point type. On HPUX, quad is a synonym for long double. It defines the types float... |
|
maxdsiz(5) -- maximum size (in bytes) of the data 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 that sets the upper limit to their size, but text, data and stack segments may have smaller maxima enforced by the maxtsiz, maxdsiz, and maxssiz tunables. This tunable defines the m... |
|
maxdsiz_64bit(5) -- maximum size (in bytes) of the data 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 that sets the upper limit to their size, but text, data and stack segments may have smaller maxima enforced by the maxtsiz, maxdsiz, and maxssiz tunables. This tunable defines the m... |
|
maxfiles(5) -- initial (soft) maximum number of file descriptors per process
|
|
maxfiles specifies the initial default number of file descriptors a process is allowed to have for open files at any given time. It is possible for a process to increase its soft limit and therefore open more than maxfiles files. Nonsuperuser processes can increase their soft limit using setrlimit() or ulimit() until they reach the hard limit, maxfiles_lim. Who Is Expected to Change This Tunable? ... |
|
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. |
