|
|
|
Traits(5) -- Lists the traits used by the Motif Toolkit.
|
|
A trait is a characteristic of a widget. A widget holding a particular trait is announcing a particular ability to other widgets. The following table summarizes the standard Motif traits. ___________________________________________________________ Purpose of Each Trait Trait Name A Widget Holding This Trait Can Do The Following: ___________________________________________________________ XmQTacces... |
|
Tttttk(5) -- ToolTalk definitions
|
|
The Tt/tttk.h header defines the following enumeration data type, with at least the following members: Tttk_op TTDT_CREATED, TTDT_DELETED, TTDT_DO_COMMAND, TTDT_GET_ENVIRONMENT, TTDT_GET_GEOMETRY, TTDT_GET_ICONIFIED, TTDT_GET_LOCALE, TTDT_GET_MAPPED, TTDT_GET_MODIFIED, TTDT_GET_SITUATION, TTDT_GET_STATUS, TTDT_GET_SYSINFO, TTDT_GET_XINFO, TTDT_LOWER, TTDT_MODIFIED, TTDT_MOVED, TTDT_OP_LAST, TTDT_O... |
|
|
Tttt_c(5) -- ToolTalk definitions
|
|
The Tt/tt_c.h header includes typedefs for the following callback functions: typedef Tt_filter_action (*Tt_filter_function)(const char *nodeid, void *context, void *accumulator); typedef Tt_callback_action (*Tt_message_callback)(Tt_message m, Tt_pattern p); To enable developers to write multithreaded applications, the header defines typedef enum tt_feature { _TT_FEATURE_MULTITHREADED = 1, // Threa... |
|
types(5) -- primitive system data types
|
|
Remarks The example given on this page is a typical version. The type names are in general expected to be present, although exceptions (if any) may be described in DEPENDENCIES. In most cases the fundamental type which implements each typedef is implementation dependent as long as source code which uses those typedefs need not be changed. In some cases the typedef is actually a shorthand for a com... |
|
UIL(5) -- The user interface language file format
|
|
The UIL language is used for describing the initial state of a user interface for a widget based application. UIL describes the widgets used in the interface, the resources of those widgets, and the callbacks of those widgets. The UIL file is compiled into a UID file using the command uil or by the callable compiler Uil(). The contents of the compiled UID file can then be accessed by the various M... |
|
unistd(5) -- standard structures and symbolic constants
|
|
The header defines the following structures and symbolic constants: Symbolic constants for the access() function: R_OK Test for read permission. W_OK Test for write permission. X_OK Test for execute (search) permission. F_OK Test for existence of file. The constants F_OK, R_OK, W_OK, and X_OK and the expressions R_OK|W_OK, R_OK|X_OK, and R_OK|W_OK|X_OK all have distinct values. Symbolic... |
|
unlockable_mem(5) -- amount of physical memory that may not be locked by user processes
|
|
Memory locking allows the privileged user to specify which pages need to remain in memory, and unaffected by the swap process. This feature allows you to ensure that memory access times are unaffected by delays introduced by memory paging and swapping. For example, locking is a tool provided to privileged users on a system that is short on physical memory. Instead of having these privileged proces... |
|
unwind(5) -- overview of stack unwind library entry points and convenience macros
|
|
The header defines the Application Programming Interface (API) of the stack unwind library, supplied as libunwind.so for HP-UX on Itanium-based systems. This page discusses the general concepts of stack unwinding and how the stack unwind library is intended to be used. It is intended to complement the section 3X manual pages describing unwind library entry points. This page also explain... |
|
v5srvtab(5) -- The server and machine keytab file
|
|
The /krb5/v5srvtab file is a file on the local node created by the rgy_edit command, the sec_create_db command, or any application that makes sec_key_mgmt() calls. The file contains passwords for servers and machine accounts. To view or manipulate the contents of this file, use the sec_key_mgmt API, described in the and the . |
|
values(5) -- machine-dependent values
|
|
This file contains a set of manifest constants, conditionally defined for particular processor architectures. The model assumed for integers is binary representation (one's or two's complement), where the sign is represented by the value of the high-order bit. BITS(type) The number of bits in a specified type (e.g., int). type) The number of bits in a specified type (e.g., int). ) The number of ... |
|
varargs(5) -- handle variable argument list
|
|
This set of macros enables programmers to write portable procedures that accept variable argument lists. Routines that have variable argument lists (such as printf()) but do not use varargs are inherently nonportable, because different machines use different argument-passing conventions (see printf(3S)). va_alist is used as the parameter list in a function header. va_dcl is a declaration for va_al... |
|
vps_ceiling(5) -- maximum (in kilobytes) of system-selectable page size
|
|
The Translation Look-aside Buffer (TLB) is a microprocessor feature for virtual memory, where the most recent physical to virtual address translations are cached, in the expectation that these translations are likely to be needed again soon. This is based on the principles of spatial and temporal locality of address references in programs. Historically, the TLB was entirely managed within hardware... |
|
vps_chatr_ceiling(5) -- maximum (in kilobytes) of user selectable page size
|
|
The Translation Look-aside Buffer (TLB) is a microprocessor feature for virtual memory, where the most recent physical to virtual address translations are cached, in the expectation that these translations are likely to be needed again soon. This is based on the principles of spatial and temporal locality of address references in programs. Historically, the TLB was entirely managed within hardware... |
|
vps_pagesize(5) -- minimum (in kilobytes) of system-selected page size
|
|
The Translation Look-aside Buffer (TLB) is a microprocessor feature for virtual memory, where the most recent physical to virtual address translations are cached, in the expectation that these translations are likely to be needed again soon. This is based on the principles of spatial and temporal locality of address references in programs. Historically, the TLB were entirely managed within hardwar... |
|
vxfs_bc_bufhwm(5) -- VxFS buffer cache high water mark(determines the VxFS buffer cache size)
|
|
VxFS maintains a buffer cache in the kernel for frequently accessed file system metadata in addition to the HP-UX kernel buffer cache that caches the file data. vxfs_bc_bufhwm tunable parameter determines the size of the VxFS buffer cache (the maximum amount of memory that can be used to cache VxFS metadata). The default value computed based on the amount of system memory ensures good system perfo... |
