|
|
|
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... |
|
sis(5) -- secure internet services with Kerberos authentication and authorization
|
|
Secure Internet Services (SIS) provides network authentication when used in conjunction with HP DCE security services, the HP Praesidium/Security Server, or other software products that provide a Kerberos V5 Network Authentication Services environment. The network authentication ensures that a local and remote host will be mutually identified to each other in a secure and trusted manner and that t... |
|
stat(5) -- data returned by the stat() function
|
|
The header defines the structure of the data returned by the functions fstat(), lstat(), and stat(). The structure stat contains at least the following members: dev_t st_dev ID of device containing file ino_t st_ino file serial number mode_t st_mode mode of file (see below) nlink_t st_nlink number of links to the file uid_t st_uid user ID of file gid_t st_gid group ID of file dev_t st... |
|
stdarg(5) -- macros for handling variable argument lists
|
|
The header contains a set of macros that can be used to write portable procedures that accept variable argument lists. Routines that have variable argument lists (such as printf()) but do not use stdarg are inherently nonportable, because different machines use different argument-passing conventions. va_list is a type defined for the variable used to traverse the list. va_start is calle... |
|
stdsyms(5) -- description of "named defines" and other specifications for
|
|
stdsyms is a description of "named defines" and other specifications that must be set by the application to obtain the appropriate name space from the HP-UX header files. HP-UX header files are organized in a manner that allows for only a subset of the symbols available in that header file to be visible to an application that conforms to a specific standard. The ANSI-C, POSIX.1, POSIX.2, and XPG... |
|
strctlsz(5) -- maximum size of streams message control (bytes)
|
|
STRCTLSZ limits the maximum number of bytes of control data that can be inserted by putmsg() in the control portion of any streams message on the system. If the tunable is set to zero, there is no limit on how many bytes can be placed in the control segment of the message. putmsg() returns [ERANGE] if the buffer being sent is larger than the current value of STRCTLSZ. Who Is Expected to Change Thi... |
|
STRCTLSZ(5) -- maximum size of streams message control (bytes)
|
|
STRCTLSZ limits the maximum number of bytes of control data that can be inserted by putmsg() in the control portion of any streams message on the system. If the tunable is set to zero, there is no limit on how many bytes can be placed in the control segment of the message. putmsg() returns [ERANGE] if the buffer being sent is larger than the current value of STRCTLSZ. Who Is Expected to Change Thi... |
|
streampipes(5) -- force all pipes to be STREAMS-based
|
|
This tunable determines the type of pipe that is created by the pipe() system call. If set to the default value of zero, all pipes created by pipe() are normal HP-UX file-system pipes. If the value is nonzero, pipe() creates STREAMS-based pipes, and STREAMS modules can be pushed onto the resulting stream. If this tunable is set to a non-zero value, the pipemod and pipedev module and driver must be... |
