|
|
|
acctresume(5) -- suspend and resume accounting when available disk space reaches threshold
|
|
The acctsuspend and acctresume tunables control when accounting stops and resumes due to disk space constraints. When free disk space on the file system being used by accounting reaches the suspension threshold, which is the acctsuspend percentage relative to the percentage of disk space available only to the superuser, accounting is suspended until such time as the free disk space reaches the res... |
|
acctsuspend(5) -- suspend and resume accounting when available disk space reaches threshold
|
|
The acctsuspend and acctresume tunables control when accounting stops and resumes due to disk space constraints. When free disk space on the file system being used by accounting reaches the suspension threshold, which is the acctsuspend percentage relative to the percentage of disk space available only to the superuser, accounting is suspended until such time as the free disk space reaches the res... |
|
|
acl(5) -- introduction to HFS access control lists
|
|
Access control lists are a key enforcement mechanism of discretionary access control (see Definitions below), for specifying access to files by users and groups more selectively than traditional HP-UX mechanisms allow. HP-UX already enables non-privileged users or processes, such as file owners, to allow or deny other users access to files and other objects on a ``need to know'' basis, as determ... |
|
aclv(5) -- introduction to JFS access control lists (ACLs)
|
|
Access control lists (ACLs) are a key enforcement mechanism of discretionary access control (see Definitions below), for specifying access to files by users and groups more selectively than traditional HP-UX mechanisms allow. HP-UX already enables non-privileged users or processes, such as file owners, to allow or deny other users access to files and other objects on a ``need to know'' basis, as... |
|
aio(5) -- POSIX asynchronous I/O facility
|
|
The POSIX Asynchronous I/O facility implements Section 6.7 of IEEE Standard 1003.1b-1993, Standard for Information Technology, Portable Operating System Interface (POSIX), Part 1: System Application Program Interface (API), Amendment 1: Realtime Extensions (C Language). It allows a process or thread to start multiple simultaneous read and/or write operations to multiple files, to wait for or obtai... |
|
aio_listio_max(5) -- the maximum number of POSIX asynchronous I/O operations that can be specified in a listio() call
|
|
This parameter places a limit on the system resources that can be consumed if a large number of POSIX asynchronous I/O operations are requested in a single listio() call. The value should be set large enough to meet system programming needs while protecting the system against excessive asynchronous I/O operations initiated by a malfunctioning process. Who Is Expected to Change This Tunable? System... |
|
aio_max_ops(5) -- maximum number of POSIX async I/O operations that can be queued at any time
|
|
This parameter places a limit on the system resources that can be consumed if large numbers of POSIX asynchronous I/O operations are queued on the system at the same time. This parameter limits the ability of competing processes to overwhelm the system with large numbers of asynchronous I/O operations and the memory they require. Each enqueued asynchronous operation requires allocation of system m... |
|
aio_monitor_run_sec(5) -- frequency of AIO thread pool monitor execution (in seconds)
|
|
The implementation of POSIX AIO on HP-UX uses kernel threads to perform I/Os to filesystems that do not directly support true asynchronous I/O. (This distinction is transparent to the user.) The kernel threads are organized into worker-thread pools (called AIO thread pools) created on a per-process basis. Since a thread pool mechanism for I/Os introduces a variety of trade-offs concerning utilizat... |
|
aio_physmem_pct(5) -- percentage of physical memory lockable for request
|
|
This parameter places a limit on how much system memory can be locked by the total number of POSIX asynchronous I/O operations that are in progress at any given time. It is important to be aware that an operation remains on the active queue and memory is not released, even if the operation is complete, until it is properly terminated by an aio_return() call for that operation. Asynchronous I/O ope... |
|
aio_prio_delta_max(5) -- greatest delta (slowdown factor) allowed in POSIX async IO request priorities
|
|
This parameter places a limit on how much the priority of a POSIX asynchronous I/O operation can be reduced to slow it down. This is the maximum priority-offset value allowed for aio_reqprio in the asynchronous-I/O control block structure aiocb. Who Is Expected to Change This Tunable? System administrators that run applications requiring heavy usage of POSIX AIO to file systems. |
|
aio_proc_threads(5) -- maximum number of process threads allowed in AIO pool
|
|
The implementation of POSIX AIO on HP-UX uses kernel threads to perform I/Os to filesystems that do not directly support true asynchronous I/O. (This distinction is transparent to the user.) The kernel threads are organized into worker-thread pools (called AIO thread pools) created on a per-process basis. Since a thread pool mechanism for I/Os introduces a variety of trade-offs concerning utilizat... |
|
aio_proc_thread_pct(5) -- percentage of all process threads allowed in AIO pool
|
|
The implementation of POSIX AIO on HP-UX uses kernel threads to perform I/Os to filesystems that do not directly support true asynchronous I/O. (This distinction is transparent to the user.) The kernel threads are organized into worker-thread pools (called AIO thread pools) created on a per-process basis. Since a thread pool mechanism for I/Os introduces a variety of trade-offs concerning utilizat... |
|
aio_req_per_thread(5) -- desirable ratio between number of pending AIO requests and servicing threads
|
|
The implementation of POSIX AIO on HP-UX uses kernel threads to perform I/Os to filesystems that do not directly support true asynchronous I/O. (This distinction is transparent to the user.) The kernel threads are organized into worker-thread pools (called AIO thread pools) created on a per-process basis. Since a thread pool mechanism for I/Os introduces a variety of trade-offs concerning utilizat... |
|
aliases(5) -- aliases file for sendmail
|
|
The newaliases command (which is the same as sendmail -bi; see sendmail(1M)) builds the sendmail alias database from a text file. The default text file is /etc/mail/aliases. Local addresses (local user names) are looked up in the alias database and expanded as necessary, unless the user name is preceded by a backslash (\). When the aliases file contains multiple entries for a given alias, only th... |
|
allocate_fs_swapmap(5) -- determines when swapmap structures are allocated for filesystem swap
|
|
The allocate_fs_swapmap tunable is used to determine whether to allocate all needed filesystem swap structures during the initialization of the filesystem swap device or wait until they are needed. Pre-allocation of all filesystem swap structures upon initialization saves time during later usage of the filesystem swap, and prevents later allocation failure due to physical memory contention. Dynami... |
