|
|
|
dttermaction(5) -- CDE terminal emulation actions
|
|
The CDE Terminal Emulation Services support the following terminal emulation actions: Dtterm Open a view of the desktop terminal emulator. Terminal Open a view of the user's preferred terminal emulator. These actions can be invoked from an application using the DtActionInvoke(3) function or invoked from a command line using the dtaction(1) utility. |
|
dttextaction(5) -- CDE text editing actions
|
|
The CDE Text Editing Services support the following text editing actions: Dtpad Open an empty view of the desktop text editor. Dtpad file Open a desktop text editor view of the text file named by the pathname in the file argument. Open file Open a view of the text file named by the pathname in the file argument. Print file Print the text file named by the pathname in the file argument. |
|
|
dttrashaction(5) -- CDE trash management actions
|
|
The CDE File Management Services support the following trash management actions: Dttrash Open a folder view of the desktop trash folder. Dttrash file Move the file named by the pathname in the file argument to the desktop trash folder. These actions can be invoked from an application using the DtActionInvoke(3) function or invoked from a command line using the dtaction(1) utility. |
|
DtWsm(5) -- workspace manager definitions
|
|
The Dt/Wsm.h header defines structures and function prototypes for workspace management services. The DtWsmWorkspaceInfo structure contains at least the following members: Atom workspace X atom name for the workspace unsigned long bg Backdrop background pixel unsigned long fg Backdrop foreground pixel Atom backdropName X atom name for backdrop int colorSetId Number of color set used char *pchTitle... |
|
dump_compress_on(5) -- selects whether the system dumps memory pages compressed or uncompressed when a kernel panic occurs.
|
|
On large systems, the time required to dump system memory when a kernel panic occurs can be excessive or even prohibitive, depending on how much physical memory is installed in the system. Compressed dump capability results in smaller and faster dumps that will also take lesser time to save over into the filesystem. The crashconf command, and its associated configuration file /etc/rc.config.d/cras... |
|
enable_idds(5) -- enable intrusion detection data source
|
|
If enable_idds is set to 1, then the HP-UX Host Intrusion Detection System (HP-UX HIDS) can enable the collection of kernel data for intrusion detection. This also causes additional things to be tracked by the kernel, resulting in a small degradation in performance (and increase in kernel memory usage), even if HP-UX HIDS is not in use. Who Is Expected to Change This Tunable? Anyone using HP-UX HI... |
|
environ(5) -- user environment
|
|
An array of strings called the environment is made available by exec(2) when a process begins. By convention, these strings have the form name=value. The following names are used by various commands (listed in alphabetical order): =value. The following names are used by various commands (listed in alphabetical order): value. The following names are used by various commands (listed in alphabetical ... |
|
eqmemsize(5) -- determines the minimum size (in pages) of the equivalently mapped reserve pool
|
|
Equivalently mapped memory is a page which has the same physical and virtual address. This is useful for some applications, and for I/O. Since most memory is to be used in the traditional swapper/virtual address model, it is useful for the system to reserve some pages for this type of access at boot while the most physical memory is available. eqmemsize provides the bottom value for the size of th... |
|
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 ... |
