|
|
|
sm.bak(4) -- statd directory and file structures
|
|
/var/statmon/sm and /var/statmon/sm.bak are directories generated by statd (see statd(1M)). Each file in /var/statmon/sm represents one or more machines to be monitored by the statd daemon. Each file in /var/statmon/sm.bak represents one or more machines to be notified by the statd daemon upon its recovery. /var/statmon/state is a file generated by statd to record its version number. This version ... |
|
snmpd.conf(4) -- configuration file for the SNMP agent
|
|
When invoked, the SNMP agent reads its configuration information from the /etc/SnmpAgent.d/snmpd.conf configuration file. The SNMP agent is either the snmpd (included with HP-UX) or the snmpd.ea (purchased with the HP OpenView product). The SNMP agent will not be able to reply if no values are configured in /etc/SnmpAgent.d/snmpd.conf i.e. /etc/SnmpAgent.d/snmpd.conf is empty. |
|
|
softkeys(4) -- keysh softkey file format
|
|
|
|
state(4) -- statd directory and file structures
|
|
/var/statmon/sm and /var/statmon/sm.bak are directories generated by statd (see statd(1M)). Each file in /var/statmon/sm represents one or more machines to be monitored by the statd daemon. Each file in /var/statmon/sm.bak represents one or more machines to be notified by the statd daemon upon its recovery. /var/statmon/state is a file generated by statd to record its version number. This version ... |
|
switch(4) -- configuration file for the name-service switch
|
|
The operating system uses a number of "databases" of information about hosts, users (passwd), groups and so forth. Data for these can come from a variety of sources: host-names and -addresses, for example, may be found in /etc/hosts, NIS, NIS+, LDAP or DNS. One or more sources may be used for each database; the sources and their lookup order are specified in the /etc/nsswitch.conf file. The foll... |
|
swpackage(4) -- product specification file (PSF) format
|
|
Introduction The swpackage command packages software into: + a distribution directory (which can be accessed directly or copied onto a CD-ROM), + a distribution tape, such as DDS, nine-track or cartridge tapes. Both directory and tape distributions use the same format. SD can read both tar and cpio tape depots. See sd(4) for details on tape format. The software is organized into a four-level hiera... |
|
symlink(4) -- symbolic link
|
|
A symbolic (or soft ) link is a file whose name indirectly refers (points) to a relative or absolute path name. During path name interpretation, a symbolic link to a relative path name is expanded to the path name being interpreted, and a symbolic link to an absolute path name is replaced with the path name being interpreted. Thus, given the path name /a/b/c/d: If c is a symbolic link to a relativ... |
|
system(4) -- system description configuration files
|
|
The HP-UX system description file describes kernel configuration information used by the kconfig(1M) and mk_kernel(1M) commands. The system description file consists of the following information: + A line specifying the version of the system file. + The list of packaged and traditional kernel modules to be configured. + Planned values for system tunable parameters, and other system-wide configurat... |
|
tar(4) -- format of tar tape archive
|
|
The header structure produced by tar (see tar(1)) is as follows (the array size defined by the constants is shown on the right): struct { char name[NAMSIZ]; (100) char mode[MODE_SZ]; (8) char uid[UID_SZ]; (8) char gid[GID_SZ]; (8) char size[SIZE_SZ]; (12) char mtime[MTIME_SZ]; (12) char chksum[CHKSUM_SZ]; (8) char typeflag; char linkname[NAMSIZ]; (100) char magic[MAGIC_SZ]; (6) char version[VERSIO... |
|
tcpd.conf(4) -- configuration file for tcpd
|
|
When inetd invokes tcpd for a service, it will read /etc/tcpd.conf and perform access control checks (see tcpd(1M)). Each line in the file is treated either as a comment or as configuration information. Commented lines begin with #. Uncommented lines contain two required fields, key and value. The fields are separated by tabs and/or spaces. A line can be continued if it terminates with a backslash... |
|
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... |
