|
|
|
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... |
|
npty(5) -- maximum number of BSD pseudo terminals (ptys)
|
|
npty is the number of pseudo terminal (pty) drivers that a system can support. The pty driver provides support for a device-pair called a pseudo terminal. A pseudo terminal is a pair of character devices, a master device, and a slave device. These allow communication between an application process and a server process. When sending data to pty devices (such as windows), a pty device must exist for... |
|
nstrevent(5) -- maximum number of outstanding STREAMS bufcalls
|
|
This tunable limits the maximum number of outstanding bufcalls that are allowed to exist in the system at any given time. This tunable is intended to protect the system against resource overload caused by the combination of modules running in all streams issuing an excessive number of bufcalls. The value selected should be equal to or greater than the combined maximum number of bufcalls that can b... |
|
NSTREVENT(5) -- maximum number of outstanding STREAMS bufcalls
|
|
This tunable limits the maximum number of outstanding bufcalls that are allowed to exist in the system at any given time. This tunable is intended to protect the system against resource overload caused by the combination of modules running in all streams issuing an excessive number of bufcalls. The value selected should be equal to or greater than the combined maximum number of bufcalls that can b... |
|
nstrpty(5) -- maximum number of STREAMS-based pseudo terminals (pts)
|
|
nstrpty is the number of STREAMS-based pseudo terminal (pts) drivers that a system can support. The pty driver provides support for a device-pair called a pseudo terminal. A pseudo terminal is a pair of character devices, a master device, and a slave device. These allow communication between an application process and a server process. When sending data to pty devices (such as windows), a pty devi... |
|
nstrpush(5) -- maximum number of STREAMS modules in a single stream
|
|
This tunable defines the maximum number of STREAMS modules that can be pushed onto a stream. This provides some protection against run-away processes that might automatically select modules to push onto a stream. It is not intended as a defense against malicious use of STREAMS modules by system users. Most systems do not require more than about three or four modules in a stream. However, there may... |
|
NSTRPUSH(5) -- maximum number of STREAMS modules in a single stream
|
|
This tunable defines the maximum number of STREAMS modules that can be pushed onto a stream. This provides some protection against run-away processes that might automatically select modules to push onto a stream. It is not intended as a defense against malicious use of STREAMS modules by system users. Most systems do not require more than about three or four modules in a stream. However, there may... |
|
nstrsched(5) -- number of STREAMS scheduler daemons to run
|
|
This tunable defines the number of multiprocessor (MP) STREAMS scheduler daemons to run on systems containing more than one processor. Note that uniprocessor (UP) systems do not use an MP scheduler daemon, but both MP and UP systems always have one UP STREAMS scheduler (supsched). If the tunable value is set to zero, the system determines how many daemons to run, based on the number of processors ... |
