|
|
|
term(4) -- format of compiled term file
|
|
Compiled terminfo descriptions are placed under the directory /usr/share/lib/terminfo. In order to avoid a linear search of a huge HP-UX system directory, a two-level scheme is used: /usr/share/lib/terminfo/c/name where c/name where /name where name where name is the name of the terminal, and c is the first character of name. Thus, hp110 can be found in the file /usr/share/lib/terminfo/h/hp110. Sy... |
|
TERM(4) -- terminal capabilities
|
|
The header contains definitions for each of the following symbolic constants and capability names in the following tables. In the following table, a Variable is the name by which a C programmer accesses a capability (at the terminfo level). A Capname is the short name for a capability specified in the terminfo source file. It is used by a person updating the source file and by the tput co... |
|
|
term.h(4) -- terminal capabilities
|
|
The header contains definitions for each of the following symbolic constants and capability names in the following tables. In the following table, a Variable is the name by which a C programmer accesses a capability (at the terminfo level). A Capname is the short name for a capability specified in the terminfo source file. It is used by a person updating the source file and by the tput co... |
|
terminfo(4) -- printer, terminal, and modem capability database
|
|
The requirements in this manpage are in effect only for implementations that claim Enhanced Curses compliance. |
|
term_c(4) -- terminal capabilities
|
|
The header contains definitions for each of the following symbolic constants and capability names in the following tables. In the following table, a Variable is the name by which a C programmer accesses a capability (at the terminfo level). A Capname is the short name for a capability specified in the terminfo source file. It is used by a person updating the source file and by the tput co... |
|
ttys(4) -- terminal control database file, for trusted systems
|
|
The system supports a single terminal control database containing entries for each local terminal that can log into the system. Authentication programs use information contained in the terminal control database to determine if login from the terminal is permitted. Additional fields are maintained for informational purposes. The format of the terminal control database file is identical to other sys... |
|
ttytype(4) -- data base of terminal types by port
|
|
ttytype is a database that identifies the kind of terminal that is attached to each tty port on the system. The file contains one line per port, and each line contains the terminal type (as a name listed in terminfo(4)), a space, and the name of the tty device file, less the initial /dev/. For example, for an HP 2622 terminal on tty02: 2622 tty02 This information is read by tset and by login (for ... |
|
tunefstab(4) -- VxFS file system tuning parameters table
|
|
The tunefstab file contains tuning parameters for VxFS file systems. tunefs sets the tuning parameters for mounted file systems by processing command line options or by reading parameters in the tunefstab file. Each entry in tunefstab is a line of fields in one of the following formats: block-device tunefs-options system-default tunefs-options block-device is the name of the device on which the fi... |
|
tztab(4) -- time zone adjustment table for date(1) and ctime(3C)
|
|
The tztab file describes the differences between Coordinated Universal Time (UTC) and local time. Several local areas can be represented simultaneously with historical detail. The file tztab consists of one or more time zone adjustment entries. The first line of the entry contains a unique string that may match the value of the TZ string in the user's environment. The format is tznamediffdstzname... |
|
udc(4) -- user-defined character raster font format
|
|
The UDC raster font format consists of a character index and character pattern. The code area and the maximum number of characters depend upon the device and the language. The size of the fonts depend upon the merged font file and the device. |
|
ups_conf(4) -- HP PowerTrust Uninterruptible Power System (UPS) monitor configuration file
|
|
The default configuration file for the HP PowerTrust UPS monitor daemon (ups_mond). Another file can be used as long as it complies with the specified format, and the monitor daemon is configured to use the alternate file (see the description of the -f option in ups_mond(1M)). Lines in the configuration file can contain a maximum of 256 characters, and the full pathname of a UPS-tty device file ca... |
|
utmp(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];... |
|
utmps(4) -- user-accounting database
|
|
File utmps contains user accounting information for all users logged onto the system. This file will be accessed by getuts(3C) only if utmpd(1M) is not running. The following information is stored in the utmps file: + User login name (up to 256 characters) + /etc/lines id + Device name (console, lnxx; up to 64 characters) + Process id + Type of entry + Exit status of a process marked as DEAD_PROCE... |
|
utmpx(4) -- utmpx database storage file
|
|
File utmpx contains user accounting information for all users logged onto the system. This file will be used instead of the utmp file, which is being depreciated. The following information is stored in the utmpx file: - User login name (up to 24 characters) - /etc/lines id - device name (console, lnxx) - process id - type of entry - exit status of a process marked as DEAD_PROCESS - the time the en... |
|
uuencode(4) -- format of an encoded uuencode file
|
|
Files output by uuencode consist of a header line followed by a number of body lines, and a trailer line. The uudecode command ignores any lines preceding the header or following the trailer (see uuencode(1)). Lines preceding a header must not look like a header. The header line consists of the word begin followed by a space, a mode (in octal), another space, and a string which specifies the name ... |
