|
|
|
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... |
|
ncsize(5) -- number of Directory Name Lookup Cache (DNLC) entries
|
|
To speed up the search through directories in the kernel, there is a memory resident cache of directories called the Directory Name Lookup Cache (DNLC). During a filename lookup in the kernel, any directories or files encountered are retained in the DNLC for future reference. The ncsize tunable dictates the number of entries in the DNLC, which is statically allocated at system boot time. Therefore... |
|
ndir(5) -- format of HP-UX directory streams
|
|
This header file defines data types used by the directory stream routines described in directory(3C). It is provided to allow older HP-UX programs to compile unmodified. This file is obsoleted starting from HP-UX 10.30 and is going to be removed in future releases. The header file described on dirent(5) should be used in all new programs for compatibility with System V Release 3, the X/... |
|
nfile(5) -- maximum number of open files (system-wide)
|
|
The nfile tunable defines the maximum number of slots in the system open file table. This number limits the cumulative number of open files by all processes in the system. In addition to named files (regular files, directories, links, device files, etc.), other objects that consume slots in the system open file table include pipes, FIFOs, sockets, streams. Be aware that the dup(2) and dup2(2) syst... |
|
nflocks(5) -- maximum number of file locks
|
|
The nflocks tunable represents the maximum number of file locks that are available system-wide. Who Is Expected to Change This Tunable? This tunable should be changed on systems expected to run applications with large number of file locks. When changing this number note that one file may have several locks, and databases that use lockf() or fcntl() may need an exceptionally large number of locks. |
|
nfs_portmon(5) -- restricts NFS services to clients from privileged ports
|
|
The nfs_portmon tunable enhances security checking on the NFS server. When set to 1, it prevents malicious users from gaining access to files exported by the NFS server. It checks whether the source port from which a request was sent is a privileged port. The range of privileged ports is 512 to 1023. Checking for privileged ports prevents users from writing their own RPC-based applications to defe... |
|
ninode(5) -- maximum number of HFS file system open inodes that can be in memory
|
|
The ninode tunable defines the number of slots in the HFS inode table. This number limits the number of open inodes that can be in memory for HFS file systems at any given time. The inode table is used as a cache memory. For performance reasons the most recent ninode (number of) open inodes are kept in main memory. The table is hashed. Each unique open file has an open inode associated with it. Th... |
|
nkthread(5) -- limits the number of threads allowed to run simultaneously
|
|
The nkthread tunable controls the absolute number of threads allowed on a system at any given time. Increasing it will allow more threads, and lowering it will restrict the number of threads. It can be determined that nkthread is too low when the kthread: table is full message is seen in the message buffer. The message can be read via dmesg or syslog. This message indicates that an application was... |
|
nproc(5) -- limits the number of processes allowed to exist simultaneously
|
|
The nproc tunable controls the absolute number of processes allowed on a system at any given time. Increasing it will allow more processes, and lowering it will restrict the number of processes. It can be determined that nproc is too low when the proc: table is full message is seen in the message buffer. The message buffer can be read via dmesg or syslog. This message indicates that an application... |
