|
|
|
vol_pattern(4) -- VERITAS Volume Manager disk group search specifications
|
|
The vol_pattern search expression language can be used in vxprint and vxedit, and with some VERITAS Volume Manager (VxVM) support library functions, to locate VERITAS Volume Manager configuration records with particular characteristics. Searches are limited to operation on one disk group at a time. In the current release, search expressions are limited to volume, plex, subdisk, DCO and snap record... |
|
vxmake(4) -- format of a vxmake description file
|
|
Descriptions of configuration records can be given to the vxmake utility either on the command line or in a file. Descriptions given on the command line can specify only one new record. Descriptions given in a description file can specify more than one record. The description file format is a convenient way of indicating record contents for other uses as well. For example, the vxprint utility can ... |
|
|
wellknownif(4) -- file for dceping(8) that contains the well-known interface IDs for core DCE and other services.
|
|
The default file contains core DCE services. Do not delete those entries. You can edit the file to include other services. The format of an entry is: server_name interface_id major_version_number minor_version_number You can obtain interface_id from the IDL header file for the server. Blank lines or lines beginning with # are ignored. You can use either spaces or tabs to separate items in a line. ... |
|
wtmp(4) -- utmp, wtmp, btmp entry format
|
|
These files, which hold user and accounting information for such commands as last, who, write, and login (see last(1), who(1), write(1), and login(1)), have the following structure as defined by : #define UTMP_FILE "/etc/utmp" #define WTMP_FILE "/var/adm/wtmp" #define BTMP_FILE "/var/adm/btmp" #define ut_name ut_user struct utmp { char ut_user[8]; /* User login name */ char ut_id[4];... |
|
wtmps(4) -- user login information
|
|
wtmps and btmps hold user and accounting information for such commands as last, who, write, and login (see last(1), who(1), write(1), and login(1)). File btmps contains bad login entries for each invalid logon attempt. File wtmps contains a record for all logins and logouts apart from accounting records. These files contain utmps-like structure, the key elements of the structure are given below: c... |
|
xtab(4) -- directories to export to NFS clients
|
|
File /etc/exports describes the directories that can be exported to NFS clients. The system administrator creates it using a text editor. mountd processes it each time a mount request is received (see mountd(1M)). /etc/exports is read automatically by the exportfs command (see exportfs(1M)). If this file is changed, exportfs must be run (exportfs -a) before the changes can affect the daemon's ope... |
|
ypfiles(4) -- Network Information Service database and directory structure
|
|
Remarks The Network Information Service (NIS) was formerly known as Yellow Pages (yp). Although the name has changed, the functionality of the service remains the same. The Network Information Service (NIS) network lookup service uses databases in the directory hierarchy under /var/yp. These databases exist only on machines that act as NIS servers. A database consists of two files created by maked... |
|
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... |
