|
|
|
event_class(5) -- The file that contains the declaration of an event class.
|
|
Audit events can be logically grouped into event classes. Event classes are defined in event class files. An event class file contains an event class number and a list of event numbers corresponding to audit events. All event class files must be created in the dcelocal/etc/audit/ec directory. The name of the event class file becomes the name of the event class. The recommended naming convention fo... |
|
executable_stack(5) -- controls whether program stacks are executable by default
|
|
This tunable parameter controls whether program stacks are executable by default. It allows systems to be configured to have extra protection from stack buffer overflow attacks without sacrificing system performance. This class of attack very commonly attempts to trick privileged programs into performing unauthorized actions or giving unauthorized access. Background information on this type of att... |
|
|
fcntl(5) -- file control options
|
|
The fcntl() function provides for control over open files. The include file describes requests and arguments to fcntl() and open(). See fcntl(2) and open(2). The access modes set by open() and accessed by fcntl() are: |
|
fenv(5) -- floating-point environment macros and functions
|
|
The header declares two types and several macros and functions to provide access to the floating-point environment. The floating-point environment refers collectively to the floating-point status flags and control modes. A floating-point status flag is a system variable whose value is set (but never cleared) when a floating-point exception is raised, which occurs as a side effect of excep... |
|
fs_async(5) -- enables write calls to return before write operation is complete (Boolean)
|
|
fs_async specifies whether or not asynchronous writing of file system data structures to disk is allowed. Synchronous writes to disk make it easier to restore file system integrity if a system crash occurs while file system data structures are being updated on the file system. If asynchronous writes are selected, HP-UX file system semantics for NFS cluster environments are preserved. In addition, ... |
|
fs_symlinks(5) -- maximum number of symbolic links used to resolve a path name
|
|
The fs_symlinks tunable represents the maximum number of symbolic links followed by the kernel when resolving a path name. Applications that create symbolic links and/or parse path names should also now use this limit represented by fs_symlinks to be consistent with the kernel. Who Is Expected to Change This Tunable? Anyone expecting to run applications using path names that may expand to a large ... |
|
fs_wrapper(5) -- configuration and binary files used by file system administration commands
|
|
The commands listed in the SYNOPSIS can operate on different types of file systems. Each command (except for mount) reads file system specific configuration files that control the command's behavior, and invokes a file system specific binary file to do the actual work. FStype is the file system type as optionally specified on the command line. If FStype is not given, then the file system type is ... |
|
group_override(5) -- The registry group override file.
|
|
The dcelocal/etc/group_override administrative file lets you override group UNIX IDs and member lists stored in the network registry database. The /etc/group_override administrative file lets you override group UNIX IDs and member lists stored in the network registry database. The group_override file functions in a similar manner as the passwd_override file that overrides principal information in ... |
|
gssapi(5) -- Generic Security Service Application Programming Interface
|
|
This introduction includes general information about the Generic Security Service Application Programming Interface (GSSAPI) defined in "Internet RFC 2743, Generic Security Service Application Programming Interface," and "RFC 2744, Generic Security Service API: C-bindings." It also includes an overview of error handling, data types, and calling conventions, including the following: Integer typ... |
|
hdlpreg_hash_locks(5) -- determines the size of the pregion spinlock pool
|
|
Global kernel structures containing information on a running process or memory usage are frequently accessed or modified by several threads concurrently. To prevent race conditions, these structures are protected by spinlocks (kernel data structures used for synchronization) which allow only the spinlock 'holder' to proceed, while all others attempting to access the structure must wait. Hashed s... |
|
hfs_revra_per_disk(5) -- maximum HFS file system blocks to be read in one
|
|
This tunable defines the maximum number of file system blocks to be read in one read-ahead operation when sequentially reading backwards. Who Is Expected to Change This Tunable? HP Field engineers, but not customers directly. When Should the Value of This Tunable Be Raised? The value of this tunable should be increased if there is a large number of reverse sequential file I/O on file systems with ... |
|
hier(5) -- file system hierarchy
|
|
The HP-UX file system is a hierarchical tree organized for administrative convenience. Within the file-system tree structure, distinct areas are provided for files that are private to one machine, files that can be shared by machines, and home directories. There are two types of files that are shared: those that can be shared by multiple machines of a common architecture, and those that can be sha... |
|
hostname(5) -- host name resolution description
|
|
Hostnames are domains. A domain is a hierarchical, dot-separated list of subdomains. For example, the machine monet, in the Berkeley subdomain of the EDU subdomain of the Internet Domain Name System would be represented as monet.Berkeley.EDU (with no trailing dot). Hostnames are often used with network client and server programs, which must generally translate the name to an address for use. (This... |
|
hosts_access(5) -- format of host access control files
|
|
The access control facility for internet services uses access control files to grant or deny access to its services. These files are defined using a simple access control language based on client (host name/address, user name) and server (process name, hostname/address) patterns. See the EXAMPLES section for a quick introduction. An extended version of the access control language is described in h... |
|
hosts_options(5) -- host access control language extensions
|
|
This manual page describes the optional extensions to the language described in the hosts_access(5) manual page. The extensible language uses the following format: daemon_list : client_list : option : option ... The first two fields are described in the hosts_access(5) manual page. Briefly, daemon_list is a list of one or more daemon process names or wildcards. client_list is a list of one or more... |
