|
|
|
remote_nfs_swap(5) -- enable swapping across NFS
|
|
This tunable controls adding a NFS filesystem for use as swap. If remote_nfs_swap is set to 0 (off), only local filesystems and devices can be used for swap. If it is set to 1 (on), both local and networked file systems can be used for swap. Historically, this tunable was used in NFS clusters that are no longer supported, but this capability has not yet been removed. Who Is Expected to Change This... |
|
rtsched_numpri(5) -- number of priority values to support for POSIX.1b realtime applications
|
|
The rtsched_numpri tunable defines how many priority values to support for POSIX 1.b realtime applications. A larger value provides additional flexibility to applications in managing relative priorities of all threads with respect to each other and with respect to other applications running in the system. However, a larger value adds processing overhead in the operating system in terms of managing... |
|
|
scroll_lines(5) -- number of scrollable lines used by the Internal Terminal Emulator
|
|
This tunable specifies the total number of scroll buffer lines used by the HP-UX graphics console Internal Terminal Emulator (ITE). This value is the sum of both on-screen and off-screen lines. For instance, if the ITE has 68 on-screen lines, and the value of scroll_lines is 128, then there will be 60 off-screen lines that can be scrolled back into view. During boot, the system may adjust the valu... |
|
scsi_maxphys(5) -- maximum allowed length of an I/O on all SCSI devices
|
|
This tunable sets the maximum data size the SCSI subsystem will accept for an I/O. Depending on the device's characteristics and the device driver configuration, the maximum size allowed by the SCSI subsystem for a particular SCSI device might be lower than or equal to this tunable's value. It will never be greater. Who Is Expected to Change This Tunable? Any customer. |
|
scsi_max_qdepth(5) -- maximum number of I/Os that target will queue up for execution
|
|
Some SCSI devices support tagged queuing, which means that they can have more than one SCSI command outstanding at any point in time. The number of commands that can be outstanding varies by device, and is not known to HP-UX. To avoid overflowing this queue, HP-UX will not send more than a certain number of outstanding commands to any SCSI device. This tunable sets the default value for that limit... |
|
sd(5) -- Software Distributor, commands to create, distribute, install, monitor, and manage software
|
|
See the Software Distributor Administration Guide, available at http://docs.hp.com for a complete description of SD. The SD command and related programs: + sd - Lets you interactively create, schedule, and monitors software jobs and log files. Also lets you launch the install, copy, and remove commands. + swacl - Modifies Access Control Lists (ACLs), which control SD security. + swagentd - Daemon ... |
|
secure_sid_scripts(5) -- controls whether setuid and setgid bits on scripts are honored
|
|
This tunable controls whether setuid and setgid bits on executable scripts have any effect. Honoring set*id on scripts make a system vulnerable to attack by malicious users. The default value for this variable is 1, indicating that set*id bits are to be ignored by the execve(2) system call for higher security. The tunable can be set to 0 for a compatibility with older releases at the expense of se... |
|
sec_audit_events(5) -- Auditable events for the security services
|
|
Code is in place for auditing security-significant events in the Security Server. Among these events are + Attempts at invoking Authentication Server/Ticket-granting Server/Privilege Server (AS/TGS/PS) operations. + Deletion of Security Server objects, including -- ACLs -- accounts -- pgo items -- registry properties -- registry/organization policies -- registry master key + Attempts at invoking a... |
|
sec_intro(5) -- Introduction to the DCE Security administrative files
|
|
This section describes DCE Security files for system administration and provides related information. The reference pages cover: aud_audit_events This file defines the auditable events for the Audit service. dts_audit_events This file defines the auditable events for the time services This page describes the auditable events for the time services. event_class This file contains the declaration of ... |
|
sema(5) -- enable or disable System V IPC semaphores at boot time
|
|
The sema tunable is obsolete. The System V IPC semaphore subsystem is always enabled. |
|
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... |
