|
|
|
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 ... |
|
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 ... |
|
nstrtel(5) -- specifies the number of telnet device files the kernel can support for incoming telnet sessions
|
|
The telnet daemon uses two STREAMS-based pseudo-terminal drivers (telm and tels). The kernel parameter, nstrtel, can be used to tune the number of pseudo-terminals. nstrtel specifies the number of kernel data structures that are created at system boot time that are required to support the device files used by incoming telnet sessions on a server. If the insf command or SAM is used to create more t... |
|
nswapdev(5) -- maximum number of devices that can be enabled for swap
|
|
Swap devices are managed in a table for easier indexing in the kernel. nswapdev sets the kernel variable responsible for the upper limit on this table, and thus the upper limit to devices which can be used for swap. Who is Expected to Change This Tunable? Anyone. |
|
nswapfs(5) -- maximum number of file systems that can be enabled for swap
|
|
File system swap devices are managed in a table for easier indexing in the kernel. nswapfs sets the kernel variable responsible for the upper limit on this table, and thus the upper limit to file systems which can be used for swap. Who is Expected to Change This Tunable? Anyone. |
|
nsysmap(5) -- number of entries in a kernel dynamic memory allocation map
|
|
This value sizes the kernel dynamic memory resource map, an array of address/length pairs that describe the free virtual space in the kernel's dynamic address space. This array has historically been statically-sized. That means certain pathological workloads that fragment the kernel address space will result in too many entries for the array. Rather than panicking when this condition occurs, the ... |
|
nsysmap64(5) -- number of entries in a kernel dynamic memory allocation map
|
|
This value sizes the kernel dynamic memory resource map, an array of address/length pairs that describe the free virtual space in the kernel's dynamic address space. This array has historically been statically-sized. That means certain pathological workloads that fragment the kernel address space will result in too many entries for the array. Rather than panicking when this condition occurs, the ... |
|
orientation(5) -- the orientation of a stream
|
|
The orientation of a stream is a property of a FILE object that is handled as a input/output stream. It is useful when the input/output model assumes that characters are handled as wide-characters within an application and stored as multi-byte characters in files, and that all the wide-character input/output functions begin executing with the stream positioned at the boundary between two multi-byt... |
|
pagezero_daemon_enabled(5) -- zeroing of free memory in the background is enabled
|
|
HP-UX provides improved security by zeroing out any memory that is being assigned to user space. This ensures that no user can read what may have been written by some other user. Normally, the zeroing is done when the physical page is allocated to the user -- often when the application touches the page for the first time. Some system calls like mlock() also result in the zeroing of pages. The time... |
