|
|
|
btmps(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... |
|
cdnode(4) -- format of a CDFS cdnode
|
|
This entry describes the cdnode structure and related concepts for the CDFS file system. The CDFS file system does not have the concept of a separate entity called an inode. The information normally found in an HFS inode is kept in a cdnode data structure. However, the cdnode data structure does not reside on the physical media, but instead is kept in kernel memory space only. The cdnode informati... |
|
|
cdrom(4) -- CD-ROM background information
|
|
This manual entry provides general information on existing CD-ROM standards, terminology, data layout, and levels of support. More detailed information is available in the standard documents listed in SEE ALSO. Not all topics discussed here are supported in the current HP-UX release. Refer to the DEPENDENCIES section for details about the contents of the current release. |
|
charmap(4) -- symbolic translation file for localedef scripts
|
|
Invoking the localedef command with the -f option causes symbolic names in the locale description file to be translated into the encodings given in the charmap file (see localedef(1M)). As a recommendation, a locale description file should be written completely with symbolic names. The charmap file has two sections: a declarations section and a character definition section. |
|
core(4) -- format of core image file
|
|
The HP-UX system writes out a file containing a core image of a terminated process when certain signals are received (see signal(5) for the list of reasons). The most common causes are memory violations, illegal instructions, floating point exceptions, bus errors, and user-generated quit signals. The core image file is called core and is written in the process's working directory (provided it is ... |
|
cpio(4) -- format of cpio archive
|
|
The header structure, when the -c option of cpio is not used (see cpio(1)), is: struct { short c_magic, c_dev; ushort c_ino, c_mode, c_uid, c_gid; short c_nlink, c_rdev, c_mtime[2], c_namesize, c_filesize[2]; char c_name[c_namesize rounded to word]; } Hdr; When the cpio -c option is used, the header information is described by: sscanf(Chdr,"%6ho%6ho%6ho%6ho%6ho%6ho%6ho%6ho%11lo%6ho%11lo", &Hdr.c... |
|
default(4) -- system default database file for a trusted system
|
|
The system default database is unique in that it defines system-wide global parameters for a trusted system. It is designed to provide values for users and devices on a global scale rather than requiring an administrator to replicate values in user or device databases when they are all the same. In addition to being easier to specify global values, it is also much easier to make a global system ch... |
|
devassign(4) -- device assignment database file for a trusted system
|
|
The system supports a single device assignment database that contains entries for local login terminals. The format of the terminal control database file is identical to other trusted system authentication database files. For more information on the file format, see authcap(4). The file consists of keyword field identifiers and values for those fields. The keyword identifiers supported and their u... |
|
dialups(4) -- dialup security control
|
|
dialups and d_passwd are used to control the dialup security feature of login (see login(1)). If /etc/dialups is present, the first word on each line is compared with the name of the line upon which the login is being performed (including the /dev/, as returned by ttyname() (see ttyname(3C)). If the login is occurring on a line found in dialups, dialup security is invoked. Anything after a space o... |
|
dir(4) -- format of directories on short-name HFS file systems
|
|
A directory behaves exactly like an ordinary file, except that no user can write into a directory. The structure of a directory entry as given in the header file is: #define DIRSIZ 14 #define DIRSIZ_CONSTANT 14 #define DIR_PADSIZE 10 #define MAXNAMLEN 255 struct direct { u_long d_ino; /* inode number of entry */ u_short d_reclen; /* length of this record */ u_short d_namlen; /* length ... |
|
disktab(4) -- disk description file
|
|
disktab is a simple database that describes disk geometries. Entries in disktab consist of a number of colon-separated fields. The first entry for each disk gives the names by which the disk is known, separated by vertical bar (|) characters. This file is provided for backward compatibility with previous HP-UX releases only. Its use is discouraged. The following list indicates the normal values st... |
|
dlpi(4) -- data link provider interface standard header file
|
|
is the standard header file containing DLPI requests as prescribed by the DLPI 2.0 standard. It contains the definitions for the primitives, acknowledgements and associated structures. The header file must be included by all DLS users (user-space and kernel-space) who intend to interact with LAN drivers through DLPI. The header file contains definitions for both connection-mode and connec... |
|
dlpi.h(4) -- data link provider interface standard header file
|
|
is the standard header file containing DLPI requests as prescribed by the DLPI 2.0 standard. It contains the definitions for the primitives, acknowledgements and associated structures. The header file must be included by all DLS users (user-space and kernel-space) who intend to interact with LAN drivers through DLPI. The header file contains definitions for both connection-mode and connec... |
|
dlpi_drv(4) -- definitions of interfaces for device drivers to interact with DLPI
|
|
The header file contains definitions of structures and function prototypes that are required by networking device drivers to interact with DLPI (data link provider interface). The header file contains interfaces that could be used by tightly coupled and loosely coupled drivers. DLPI serves as a sole interface to DLS users for tightly coupled drivers. Whereas, a loosely coupled driver ... |
|
dlpi_drv.h(4) -- definitions of interfaces for device drivers to interact with DLPI
|
|
The header file contains definitions of structures and function prototypes that are required by networking device drivers to interact with DLPI (data link provider interface). The header file contains interfaces that could be used by tightly coupled and loosely coupled drivers. DLPI serves as a sole interface to DLS users for tightly coupled drivers. Whereas, a loosely coupled driver ... |
