|
|
|
mfconv(5) -- Mainframe code set conversion
|
|
Provide code set conversion between Mainframe and HP-UX Japanese code sets. These code conversions are available by iconv(1) command and iconv(3C) function. Following Mainframe code sets are supported for code conversions: |
|
mknod(5) -- header file of macros for handling device numbers
|
|
The header file defines macros to create and interpret device identification numbers for use with the mknod() system call (see mknod(2)). The use of these macros is architecture-dependent. See the System Administration Manual for your system for information on how to select major and minor device numbers. mknod.h contains the macro dev_t makedev(int major, int minor) which packs the ... |
|
|
mknod.h(5) -- header file of macros for handling device numbers
|
|
The header file defines macros to create and interpret device identification numbers for use with the mknod() system call (see mknod(2)). The use of these macros is architecture-dependent. See the System Administration Manual for your system for information on how to select major and minor device numbers. mknod.h contains the macro dev_t makedev(int major, int minor) which packs the ... |
|
mm(5) -- the MM macro package for formatting documents
|
|
This package provides a formatting capability for a very wide variety of documents. The manner in which a document is typed in and edited is essentially independent of whether the document is to be eventually formatted at a terminal or is to be phototypeset. See the references below for further details. The -mm option causes nroff(1) and troff to use the non-compacted version of the macro package. |
|
mman(5) -- memory mapping definitions
|
|
The header defines the following symbolic constants for use with the madvise() function: MADV_NORMAL No further special treatment. MADV_RANDOM Expect random page references. MADV_SEQUENTIAL Expect sequential page references. MADV_WILLNEED Will need these pages. MADV_DONTNEED Will not need these pages. MADV_SPACEAVAIL Ensure that resources are reserved. The following symbolic constants... |
|
msgmap(5) -- number of entries in the System V IPC message space resource map
|
|
The msgmap tunable specifies the size of (number of entries in) the message space resource map that tracks the free space in shared IPC message space. Each resource map entry is an offset-space pair which points to the offset and size (bytes) of each contiguous series of unused message space "segments". If the map is full when message segments are released (e.g., by msgrcv()), the system issues ... |
|
msgmax(5) -- maximum System V IPC message size in bytes
|
|
The msgmax tunable specifies the maximum allowable size, in bytes, of any single message in a System V message queue. msgmax must be no larger than msgmnb (the size of a queue) nor can it be larger than the preallocated system-wide message storage space (msgssz*msgseg). Possible strategies for deciding this tunable value include setting it equal to msgmnb (one message per queue) or the size of the... |
|
msgmnb(5) -- maximum number of bytes on a single System V IPC message queue
|
|
The msgmnb tunable specifies the maximum allowable total combined size, in bytes, of all messages queued in a single given System V IPC message queue at any one time. If a msgsnd() system call attempts to exceed the limit imposed by msgmnb, it will block (or return [EAGAIN] if IPC_NOWAIT was specified) until a caller of msgrcv() decreases the number of bytes in the queue sufficiently such that the... |
|
msgmni(5) -- maximum number of system-wide System V IPC message queues (IDs) allowed
|
|
The msgmni tunable specifies the maximum number of system-wide System V IPC message queue identifiers (one per queue). Each message queue created has an identifier (ID) and there is an upper limit of msgmni identifiers. Applications use the msgget() system call to create new queues. If all IDs have been used, msgget() will return [ENOSPC]. If a process acquires a message queue, but the process ter... |
|
msgseg(5) -- number of System V IPC message segments in the system
|
|
The msgseg specifies the total number of "segments" of system-wide shared memory message storage space which is shared among all IPC message queues. The total available space for messages in the system is defined by the product of msgseg*msgssz, the number of segments multiplied by the segment size. Segments are only used to store messages larger than 64 bytes long. Messages smaller than or equa... |
|
msgssz(5) -- number of bytes in a System V IPC message segment
|
|
The msgssz tunable specifies the size, in bytes, of a "segment" of memmory space reserved for storing IPC messages. Space for messages is acquired in segment-sized increments as required to contain the message. Separate messages do not share segments. Messages of size less than or equal to 64 bytes are allocated in a different area and do not require a segment. The total available space for mess... |
|
msgtql(5) -- maximum number of System V IPC messages in the system at any time
|
|
The msgtql tunable specifies the maximum total system-wide individual messages across all message queues. Every message has a header to specify message type and location and the total number of headers is limited by msgtql. Note that if a msgsnd() system call attempts to exceed the limit imposed by msgtql, it will block until message space becomes available or return [EAGAIN] if IPC_NOWAIT is set.... |
|
nbuf(5) -- TO BE OBSOLETED
|
|
These tunables, traditionally used for sizing a static buffer cache, are deprecated. The recommended way to configure a static buffer cache is to set the tunables dbc_min_pct and dbc_max_pct to the same value. Please refer to dbc_min_pct(5) and dbc_max_pct(5), or consult HP support for more information. Note that bufpages and nbuf were specified in units of 4K physical pages, and dbc_min_pct and d... |
|
ncdnode(5) -- maximum number of open CDFS files (system-wide)
|
|
ncdnode defines the number of slots in the inode table for in the CDROM file systems (CDFS). This number limits the number of open nodes that can be in memory for CDFS file systems at any given time. It is functionally similar to ninode but applies only to CD-ROM file systems. Who Is Expected to Change This Tunable? This tunable may need to be modified on systems that run applications requiring ac... |
|
nclist(5) -- number of cblocks for pty and tty data transfers
|
|
nclist specifies how many cblocks are allocated in the system. Data traffic is stored in cblocks as it passes through tty and pty devices. The default value for nclist, 8292, is based on a formula of 100 cblocks for system use in handling traffic to the console, etc., plus an average of 16 cblocks per user session, assuming 512 user sessions. cblocks are also used for serial connections other than... |
