|
|
semaem(5) -- adjust-on-exit maximum value
|
|
The semaem tunable specifies maximum cumulative "undo" value for any one semaphore as changed any one single process. That is, a process is allowed up to semaem outstanding increments or decrements on a semaphore for which SEM_UNDO has been specified. If an application attempts to exceed the limit, it will receive an [ERANGE] error from semop(). For more information about System V semaphores, re... |
|
semmni(5) -- number of System V IPC system-wide semaphore identifiers
|
|
The semmni tunable specifies the maximum number of System V IPC system-wide semaphore sets (and identifiers) which can exist at any given time. A single identifier (ID) is returned for each semget() system call to create a new set of one or more (up to semmsl) semaphores. If an application attempts to create a semaphore set when all IDs have previously been allocated, it will receive an [ENOSPC] e... |
|
semmns(5) -- number of System V IPC system-wide semaphores
|
|
The semmns tunable specifies the maximum total individual System V IPC system-wide semaphores which can be assigned by applications. Semaphores are assigned in "sets" associated with an ID. Thus semaphores can be distributed in any manner across the range of IDs with one or more per ID. There is no reason to specify semmns less than semmni (the maximum number of identifiers) as each ID requires ... |
|
semmnu(5) -- maximum number of System V IPC undo structures for processes
|
|
The semmnu tunable specifies the maximum number of System V IPC system-wide processes that can have "undo" operations pending at any given time. If an application exhausts this limit, it will receive an [ENOSPC] error from semop(). For more information about System V semaphores, refer to the Overview section of the sema(5) manpage. Who Is Expected to Change This Tunable? Anyone. |
|
semmsl(5) -- maximum number of System V IPC semaphores per identifier
|
|
The semmsl tunable specifies the maximum number of individual System V IPC semaphores per semaphore identifier (ID). If an application attempts to exceed this limit, it will receive an [EINVAL] error from semget(). For more information about System V semaphores, refer to the Overview section of the sema(5) manpage. Who Is Expected to Change This Tunable? Anyone. When Should the Value of This Tunab... |
|
semume(5) -- maximum number of System V IPC undo entries per process
|
|
The semume tunable specifies the maximum number of System V IPC semaphores upon which a single process can have outstanding (non-zero) "undo" operations. If an application exhausts this limit, it will receive an [EINVAL] error from semop(). For more information about System V semaphores, refer to the Overview section of the sema(5) manpage. Who Is Expected to Change This Tunable? Anyone. |
|
semvmx(5) -- maximum value of any single System V IPC semaphore
|
|
The semvmx tunable specifies the maximum value any given System V IPC semaphore can have. If an application attempt to exceed this limit, it will receive an [ERANGE] error from semop() or from semctl(). For more information about System V semaphores, refer to the Overview section of the sema(5) manpage. Who Is Expected to Change This Tunable? Anyone. |
|
sendfile_max(5) -- maximum number of Buffer Cache Pages used by sendfile
|
|
This variable is used to limit how many Buffer Cache Pages the sendfile() system call can use. This might be useful in a machine that has a large sendfile() load but is limited in memory. Who Is Expected to Change This Tunable? Anyone. |
|
shmem(5) -- enable or disable System V shared memory
|
|
The shmem tunable is obsolete. The System V IPC shared memory subsystem is always enabled. Shared memory is an efficient InterProcess Communications (IPC) mechanism. One process creates a shared memory segment and attaches it to its address space. Any processes looking to communicate with this process through the shared memory segment, then attach the shared memory segment to their corresponding a... |
|
shmmax(5) -- maximum size (in bytes) for a System V shared memory segment
|
|
Shared memory is an efficient InterProcess Communications (IPC) mechanism. One process creates a shared memory segment and attaches it to its address space. Any processes looking to communicate with this process through the shared memory segment, then attach the shared memory segment to their corresponding address spaces as well. Once attached, a process can read from or write to the segment depen... |
|
shmmni(5) -- number of System V shared memory segment identifiers in the system
|
|
Shared memory is an efficient InterProcess Communications (IPC) mechanism. One process creates a shared memory segment and attaches it to its address space. Any processes looking to communicate with this process through the shared memory segment then attach the shared memory segment to their corresponding address spaces as well. Once attached, a process can read from or write to the segment depend... |
|
shmseg(5) -- maximum number of System V shared memory segments per process
|
|
Shared memory is an efficient InterProcess Communications (IPC) mechanism. One process creates a shared memory segment and attaches it to its address space. Any processes looking to communicate with this process through the shared memory segment then attach the shared memory segment to their corresponding address spaces. Once attached, a process can read from or write to the segment depending on t... |
|
signal(5) -- description of signals
|
|
The header defines the following symbolic constants, each of which expands to a distinct constant expression of the type: void (*)(int) whose value matches no declarable function. SIG_DFL Request for default signal handling. SIG_ERR Return value from signal() in case of error. SIG_HOLD Request that signal be held. SIG_IGN Request that signal be ignored. The following data types are defi... |
