|
|
|
.netrc(4) -- login information for ftp and rexec
|
|
The .netrc file contains login and initialization information used by the ftp autologin process, by the rexec() library routine, and by the rexec command (see ftp(1), rexec(3N), and remsh(1)), respectively. This file is optional. It exists, if at all, in the user's home directory. If the .netrc file contains password or account information for use other than for anonymous ftp, its owner must matc... |
|
.rhosts(4) -- security files authorizing access by remote hosts and users on local host
|
|
The /etc/hosts.equiv file and files named .rhosts found in users' home directories specify remote hosts and users that are "equivalent" to the local host or user. Users from equivalent remote hosts are permitted to access a local account using rcp or remsh or to rlogin to the local account without supplying a password (see rcp(1), remsh(1), and rlogin(1)). The security provided by hosts.equiv i... |
|
|
a.out(4) -- assembler and link editor output
|
|
ELF a.out The file name a.out is the default output file name from the link editor, ld(1). The link editor will make an a.out executable if there were no errors in linking. The output file of the assembler, as(1), also follows the format of the a.out file although its default file name is different. Programs that manipulate ELF files may use the library that elf(3E) describes. An overview of the f... |
|
acct(4) -- per-process accounting file format
|
|
Files produced as a result of calling acct() (see acct(2)) have records in the form defined by , whose contents are: typedef ushort comp_t; /* "floating point": 13-bit fraction, 3-bit exponent */ struct acct { char ac_flag; /* Accounting flag */ char ac_stat; /* Exit status */ uid_t ac_uid; /* Accounting user ID */ gid_t ac_gid; /* Accounting group ID */ dev_t ac_tty; /* control type... |
|
ar(4) -- common archive file format
|
|
The ar command is used to concatenate several files into an archive file (see ar(1)). Archives are used mainly as libraries to be searched by the link editor (see ld(1)). Each archive begins with the archive magic string. #define ARMAG "!\n" /* magic string */ #define SARMAG 8 /* length of magic string */ Following the archive magic string are the archive file members. Each file member is... |
|
audeventsta(4) -- define and describe audit system events
|
|
The /usr/audit/audeventstab file lists audit event numbers, corresponding mnemonic names, and brief explanations of each event. Blank lines and comments (beginning with a # character) are allowed. Each non-comment, non-blank line in this file contains three parts: event Audit event number in decimal: a single field separated by whitespace. name Corresponding mnemonic name: a single field separated... |
|
audit(4) -- file format and other information for auditing
|
|
Audit records are generated when users make security-relevant system calls, as well as by self-auditing processes that call audwrite() (see audwrite(2)). Access to the auditing system is restricted to superuser. Each audit record consists of an audit record header and a record body. The record header is comprised of time, process ID, error, event type, and record body length. The time refers to th... |
|
authcap(4) -- security databases for trusted systems
|
|
All security-relevant databases are stored in an ASCII format in the file system. This format is converted to binary structures by support routines described in Section 3 manual entries. This manual entry describes the format of these databases, and describes the philosophy of conversion into data structures. |
|
bootconf(4) -- boot device configuration table
|
|
This file, /stand/bootfonf, contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the Software Distributor and HP-UX kernel control scripts (fileset OS- Core.KERN-RUN) to determine how and where to update the initial boot loader. Normally the kernel's checkinstall script queries the system's hardware and creates the file. In rare cases when either ... |
|
btmp(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];... |
|
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 ... |
|
dlpi_ext(4) -- HP-specific extensions for DLPI
|
|
is the header file for HP-specific extensions to data link provider interface, DLPI 2.0 standard. The header file contains definitions for primitives, acknowledgements, ioctls and associated structures to satisfy needs of DLS users over and beyond what is provided by DLPI 2.0 standard. The header file must be included by all DLS users (user-space and kernel-space) who intend to intera... |
|
dlpi_ext.h(4) -- HP-specific extensions for DLPI
|
|
is the header file for HP-specific extensions to data link provider interface, DLPI 2.0 standard. The header file contains definitions for primitives, acknowledgements, ioctls and associated structures to satisfy needs of DLS users over and beyond what is provided by DLPI 2.0 standard. The header file must be included by all DLS users (user-space and kernel-space) who intend to intera... |
|
dosif(4) -- DOS Interchange Format description
|
|
The commands doschmod, doscp, dosdf, dosls, dosll, dosmkdir, dosrm, and dosrmdir are targeted for removal from HP-UX. Use the dos2ux and ux2dos commands to convert files between HP-UX and DOS file formats; see dos2ux(1). DOSIF (DOS Interchange Format) is the name given to the media format used by the DOS operating system. This format is based upon that used in IBM PC and PC AT and HP Vectra system... |
|
dp(4) -- dedicated ports file used by DDFA software and Telnet port identification feature
|
|
The dp file has two uses: Datacommunications and Terminal Controller Device File Access The dp file is used by the Datacommunications and Terminal Controller Device File Access (DDFA) software to allow terminal server ports to be programmatically accessed from HP-UX applications in the same way as devices connected directly to the HP-UX system. It contains a one-line entry for each configured term... |
|
d_passwd(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... |
|
efi(4) -- Extensible Firmware Interface description
|
|
The EFI (Extensible Firmware Interface) is an interface between HP-UX and the Itanium-based platform firmware. The file system supported by the Extensible Firmware Interface is based on the FAT file system. EFI encompasses the use of FAT-32 for a system partition, and FAT-12 or FAT-16 for removable media. The system partition is required on a bootable disk for the Itanium-based platform. For a har... |
|
exports(4) -- directories to export to NFS clients
|
|
File /etc/exports describes the directories that can be exported to NFS clients. The system administrator creates it using a text editor. mountd processes it each time a mount request is received (see mountd(1M)). /etc/exports is read automatically by the exportfs command (see exportfs(1M)). If this file is changed, exportfs must be run (exportfs -a) before the changes can affect the daemon's ope... |
|
fspec(4) -- format specification in text files
|
|
It is sometimes convenient to maintain text files on the HP-UX system with non-standard tabs, (meaning tabs that are not set at every eighth column). Generally, such files must be converted to a standard format - frequently by replacing all tabs with the appropriate number of spaces - before they can be processed by HP-UX system commands. A format specification occurring in the first line of a tex... |
|
fstab(4) -- static information about the file systems
|
|
fstab is an ASCII file that resides in directory /etc. Programs read it, but do not write to or from it. System administrators are responsible for creating and maintaining this file properly. /etc/fstab contains a list of mountable file-system entries. Each file-system entry appears on a separate line, and consists of fields separated by one or more blanks or tabs. The order of entries in /etc/fst... |
|
fs_vxfs(4) -- format of a VxFS file system volume
|
|
The VxFS super-block always begins at byte offset 8192 from the start of the file system. The super-block location is fixed so that various system utilities know where to locate it. Super-block fields contain the following fundamental sizes and offsets: fs_bsize The block size of the file system. VxFS supports block sizes of 1024, 2048, 4096, and 8192 bytes. The default block size depends on the s... |
|
ftpaccess(4) -- ftpd configuration file
|
|
The /etc/ftpd/ftpaccess file is used to configure the operation of ftpd (see ftpd(1M)). |
|
ftpconversions(4) -- ftpd conversions database
|
|
The conversions known by ftpd and their attributes are stored in an ASCII file that is structured as below. Each line in the file provides a description for a single conversion. Fields are separated by colons (:). %s:%s:%s:%s:%s:%s:%s:%s 1 2 3 4 5 6 7 8 Field Description 1 strip prefix 2 strip postfix 3 addon prefix 4 addon postfix 5 external command 6 types 7 options 8 description strip postfix a... |
|
ftpgroups(4) -- group password file for use with the SITE GROUP and SITE GPASS commands.
|
|
The ftpgroups file is the group password file for use with the SITE GROUP and SITE GPASS commands. To enable the use of this file, the entry private yes must be made in the configuration file /etc/ftpd/ftpaccess. This file contains an alphanumeric string, encrypted password, and the actual group name from the /etc/group file. Each entry is separated by :. After a user logs in, the SITE GROUP and S... |
|
ftphosts(4) -- ftpd individual user host access file
|
|
The /etc/ftpd/ftphosts file is used to allow or deny access to certain accounts from various hosts. |
|
ftpservers(4) -- ftpd virtual hosting configuration specification file
|
|
The /etc/ftpd/ftpservers file is used to tell which set of virtual domain configuration files that the ftpd server should use. With VIRTUAL support, wu-ftpd has the ability to use separate configuration files for each virtual domain. For a virtual host, configuration files can be placed into a separate virtual domain directory. The directory path and the virtual host IP address that is to use thos... |
|
ftpusers(4) -- security file for ftpd(1M)
|
|
ftpd rejects remote logins to local user accounts that are named in /etc/ftpd/ftpusers. Each restricted account name must appear alone on a line in the file. The line cannot contain any white space. User accounts that specify a restricted login shell in /etc/passwd should be listed in /etc/ftpd/ftpusers because ftpd accesses local accounts without using their login shells. UUCP accounts should be ... |
|
gated-confi(4) -- GateDaemon Configuration Guide
|
|
Configuration Overview + Introduction + Statement Summary + Preferences and Route Selection + Trace Statements and Global Options + Directive Statements + Options Statements + Interface Statements and Configuration + Definition Statements |
|
gated.conf(4) -- GateDaemon Configuration Guide
|
|
Configuration Overview + Introduction + Statement Summary + Preferences and Route Selection + Trace Statements and Global Options + Directive Statements + Options Statements + Interface Statements and Configuration + Definition Statements |
|
gated.config(4) -- GateDaemon Configuration Guide
|
|
Configuration Overview + Introduction + Statement Summary + Preferences and Route Selection + Trace Statements and Global Options + Directive Statements + Options Statements + Interface Statements and Configuration + Definition Statements |
|
gettydefs(4) -- speed and terminal settings used by getty
|
|
The /etc/gettydefs file contains information used by getty to set up the speed and terminal settings for a line (see getty(1M)). It supplies information on what the login prompt should look like. It also supplies the speed to try next if the user indicates the current speed is not correct by typing a Break character. Each entry in /etc/gettydefs has the following format: label# # initial-flags # f... |
|
group(4) -- group file, grp.h
|
|
group contains for each group the following information: + group name + encrypted password + numerical group ID + comma-separated list of all users allowed in the group This is an ASCII file. Fields are separated by colons, and each group is separated from the next by a new-line. No spaces should separate the fields or parts of fields on any line. If the password field is null, no password is asso... |
|
hosts(4) -- host name data base
|
|
The file /etc/hosts associates Internet (IP) addresses with official host names and aliases. This allows a user to refer to a host by a symbolic name instead of an Internet address. Note: This file must contain all addresses for local interfaces that ifconfig needs at boot time (see ifconfig(1M)). When using the name server (see named(1M)), or Network Information Service (see ypserv(1M)), this fil... |
|
hosts.equiv(4) -- security files authorizing access by remote hosts and users on local host
|
|
The /etc/hosts.equiv file and files named .rhosts found in users' home directories specify remote hosts and users that are "equivalent" to the local host or user. Users from equivalent remote hosts are permitted to access a local account using rcp or remsh or to rlogin to the local account without supplying a password (see rcp(1), remsh(1), and rlogin(1)). The security provided by hosts.equiv i... |
|
inetd.conf(4) -- configuration file for inetd
|
|
On invocation, the inetd daemon reads its configuration information from the /etc/inetd.conf configuration file, and possibly at some later time in response to a SIGHUP signal (see inetd(1M)). Each line in the file is treated either as a comment or as configuration information for a given service Comments are denoted by a # at the beginning of a line. Noncomment lines contain seven or nine require... |
|
inetd.sec(4) -- optional security file for inetd
|
|
When inetd accepts a connection from a remote system, it checks the address of the host requesting the service against the list of hosts to be allowed or denied access to the specific service (see inetd(1M)). The file inetd.sec allows the system administrator to control which hosts (or networks in general) are allowed to use the system remotely. This file constitutes an extra layer of security in ... |
|
inetsvcs.conf(4) -- configuration file for secure internet services
|
|
The internet services, ftp, rcp, remsh, rlogin and telnet, use the /etc/inetsvcs.conf configuration file to decide their behavior (i.e., whether to allow network authentication using Kerberos V5 or not). The contents of the file decide whether the secure internet services are to be enabled or not. This configuration file is updated by the program inetsvcs_sec. The default entry in the file is as f... |
|
info(4) -- diskless client configuration information file
|
|
The info file is a POSIX shell sourceable file which contains parameter definitions used at boot time. Typically, it will be an empty file and default values will be used for all parameters. Following is the list of parameters which can be defined in the info file: ROOT_SERVER_IP Specifies the IP address of the client's private root server. If this is not specified, the client's private root ser... |
|
inittab(4) -- script for the boot init process
|
|
The /etc/inittab file supplies the script to the boot init daemon in its role as a general process dispatcher (see init(1M)). The process that constitutes the majority of boot init's process dispatching activities is the line process /usr/sbin/getty that initiates individual terminal lines. Other processes typically dispatched by boot init are daemons and shells. The inittab file is composed of e... |
|
inode_vxfs(4) -- format of a VxFS file system inode
|
|
A VxFS inode is typically 256 bytes in length, but an inode can also be 512 bytes. You specify the inode size with mkfs. An inode entry has the following format: i_mode The mode and type of file. i_nlink The number of links to the file. i_uid The inode owner. i_gid The inode group. i_size The size in bytes of the file. Eight bytes are allocated. i_atime Time of last access, in struct timeval forma... |
|
intro(4) -- introduction to file formats
|
|
This section outlines the formats of various files. The C struct declarations for the file formats are given where applicable. Usually, these structures can be found in directories /usr/include or /usr/include/sys. |
|
ioconfig(4) -- ioconfig entry format
|
|
The ioconfig file is used to retain information on system's IO configuration across reboots. It contains two types of information: + Mappings of dynamically allocated major numbers to drivers. + Mappings of instance numbers to hardware paths. At boot time this file is read and the information is stored in the io_tree kernel data structure. The ioconfig file is created by insf at install time; and... |
|
issue(4) -- issue identification file
|
|
The file /etc/issue contains the issue or project identification to be printed as a login prompt. This is an ASCII file which is read by the getty program then written to any terminal spawned or respawned from the inittab file. |
|
krb5.conf(4) -- Kerberos configuration file
|
|
The configuration file, krb5.conf, contains information needed by the Kerberos V5 library. This includes information describing the default Kerberos realm and the location of the Kerberos key distribution centers for known realms. The krb5.conf file uses an INI-style format. Sections are delimited by square braces, [ ]. Within each section, there are relations where tags can be assigned to have sp... |
|
libgss(4) -- shared library for GSSAPI (Generic Security Service Application Programming Interface)
|
|
libgss is a shared library which contains all the GSSAPIs as per the RFC 2743 and implemented as C-language interfaces as defined in the RFC 2744, Generic Security Service API : C-bindings. GSSAPI provides security services for applications independent of the various underlying security mechanisms. The services include authentication, integrity and/or confidentiality services. GSSAPI provides secu... |
|
lif(4) -- logical interchange format description
|
|
LIF (Logical Interchange Format) is a Hewlett-Packard standard massstorage format that can be used for interchange of files among various HP computer systems. A LIF volume contains a header (identifying it as a LIF volume) and a directory that defines the contents (i.e. files) of the volume. The size of the directory is fixed when the volume is initialized (see lifinit(1)) and sets an upper bound ... |
|
localedef(4) -- format and semantics of locale definition file
|
|
This is a description of the syntax and meaning of the locale definition that is provided as input to the localedef command to create a locale (see localedef(1M)). The following is a list of category tags, keywords and subsequent expressions which are recognized by localedef. The order of keywords within a category is irrelevant with the exception of the copy keyword and other exceptions noted und... |
|
logingroup(4) -- group file, grp.h
|
|
group contains for each group the following information: + group name + encrypted password + numerical group ID + comma-separated list of all users allowed in the group This is an ASCII file. Fields are separated by colons, and each group is separated from the next by a new-line. No spaces should separate the fields or parts of fields on any line. If the password field is null, no password is asso... |
|
lvmpvg(4) -- LVM physical volume group information file
|
|
lvmpvg is an ASCII file that stores the volume-group information for all of the physical volume groups in the system. The information is stored in a hierarchical format. First, it starts with a volume group under which multiple physical volume groups can exist. Under each physical volume group, a list of physical volumes can be specified. There must be at least one physical volume group in each vo... |
|
magic(4) -- magic numbers for HP-UX implementations
|
|
The magic.h file localizes all information about HP-UX ``magic numbers'' in one file, thus facilitating uniform treatment of magic numbers. This file specifies the location of the magic number in a file (always the start of the file) and the structure of the magic number: struct magic_number { unsigned short system_id; unsigned short file_type; }; typedef struct magic_number MAGIC; magic.h inclu... |
|
mnttab(4) -- mounted file system table
|
|
mnttab resides in directory /etc and contains a table of devices mounted by the mount command (see mount(1M)). The file contains a line of information for each mounted filesystem which is structurally identical to the contents of /etc/fstab described by fstab(4). There are a number of lines of the form: special_file_name dir type opts freq passno mount_time consisting of entries similar to: /dev/d... |
|
model(4) -- HP-UX machine identification
|
|
There are certain inevitable distinctions between HP-UX implementations due to hardware differences. Where such distinctions exist, conditional compilation or other definitions can be used to isolate the differences. Flags and typedefs to resolve these distinctions are collected in the header file which contains constants identifying various HP-UX implementations. For example, header fil... |
|
named.conf(4) -- configuration file for NameDaemon
|
|
BIND 9 configuration is broadly similar to BIND 8.x. However, there are a few new areas of configuration, such as views. BIND 8.x configuration files should work with few alterations in BIND 9.2, although more complex configurations need to be reviewed to check if they can be more efficiently implemented using the new features implemented in BIND 9.2. BIND 4.9.7 configuration files can be converte... |
|
netconfig(4) -- network configuration database
|
|
The network configuration database, /etc/netconfig, is a system file used to store information about networks that are connected to the system. The netconfig database and the routines that access it (see getnetconfig(3N)) are part of the Network Selection component. The Network Selection component also includes getnetpath() routines to provide application-specific network search paths. These routi... |
|
netgroup(4) -- list of network groups
|
|
File /etc/netgroup defines network-wide groups, and is used for permission checking when executing remote mounts, remote logins, and remote shells. For remote mounts, the information in netgroup classifies machines; for remote logins and remote shells, it classifies users. Each line of the netgroup file defines a group and has the format groupname member1 member2 ... where memberi is either anothe... |
|
netrc(4) -- login information for ftp and rexec
|
|
The .netrc file contains login and initialization information used by the ftp autologin process, by the rexec() library routine, and by the rexec command (see ftp(1), rexec(3N), and remsh(1)), respectively. This file is optional. It exists, if at all, in the user's home directory. If the .netrc file contains password or account information for use other than for anonymous ftp, its owner must matc... |
|
nettlgen.co(4) -- network tracing/logging and kernel logging configuration file
|
|
/etc/nettlgen.conf, the configuration file for Common Network Tracing/Logging and Kernel Logging commands commands, contains configuration information used by the nettl, kl, and netfmt commands (see nettl(1M), kl(1M), and netfmt(1M)). The nettlconf command (see nettlconf(1M)) maintains network and kernel log and subsystem data in this file, allowing subsystems to safely add, modify, or delete exis... |
|
nettlgen.conf(4) -- network tracing/logging and kernel logging configuration file
|
|
/etc/nettlgen.conf, the configuration file for Common Network Tracing/Logging and Kernel Logging commands commands, contains configuration information used by the nettl, kl, and netfmt commands (see nettl(1M), kl(1M), and netfmt(1M)). The nettlconf command (see nettlconf(1M)) maintains network and kernel log and subsystem data in this file, allowing subsystems to safely add, modify, or delete exis... |
|
networks(4) -- network name data base
|
|
The /etc/networks file associates Internet (IP) addresses with official network names and aliases. This allows the user to refer to a network by a symbolic name instead of using an Internet address. For each network, a single line should be present with the following information: Aliases are other names under which a network is known. For example:... |
|
nisfiles(4) -- NIS+ database files and directory structure
|
|
The Network Information Service Plus (NIS+) uses a memory-based, replicated database. This database uses a set of files in the /var/nis directory for checkpointing to stable storage and for maintaining a transaction log. Additionally, the NIS+ server and client use files in this directory to store binding and state information. The NIS+ service implements an authentication and authorization system... |
|
nlist(4) -- nlist and nlist64 structure formats
|
|
nlist() and nlist64() can be used to extract information from the symbol table in an object file (see nlist(3E)). They are basically the same tool, and both can process SOM and Elf files. Since symbol tables are machine dependent (as defined in each implementation's copy of ), a header file, nlist.h is defined to encapsulate the differences. The nlist function, either nlist() or nlist64(... |
|
nlist64(4) -- nlist and nlist64 structure formats
|
|
nlist() and nlist64() can be used to extract information from the symbol table in an object file (see nlist(3E)). They are basically the same tool, and both can process SOM and Elf files. Since symbol tables are machine dependent (as defined in each implementation's copy of ), a header file, nlist.h is defined to encapsulate the differences. The nlist function, either nlist() or nlist64(... |
|
nlist_ia(4) -- nlist and nlist64 structure formats
|
|
nlist() and nlist64() can be used to extract information from the symbol table in an object file (see nlist(3E)). They are basically the same tool, and both can process SOM and Elf files. Since symbol tables are machine dependent (as defined in each implementation's copy of ), a header file, nlist.h is defined to encapsulate the differences. The nlist function, either nlist() or nlist64(... |
|
nlist_pa(4) -- nlist and nlist64 structure formats
|
|
nlist() and nlist64() can be used to extract information from the symbol table in an object file (see nlist(3C)). They are basically the same tool except nlist() can only process SOM files on a PA-RISC 32-bit system while nlist64() can process SOM and ELF files on either a PA-RISC 32-bit or 64-bit system. Since symbol tables are machine dependent (as defined in each implementation's copy of |
|
nlspath(4) -- NLSPATH configuration file
|
|
The file /etc/default/nlspath allows the superuser to restrict the paths set by others through an environment variable NLSPATH to locate message catalogs for setuid or setgid root programs. This file contains only one entry with the following format: NLSPATH=pseudo-pseudo-pathname:pseudo-:pseudo-pseudo-pathname:... :... pseudo-pathnames must be separated by a colon. The paths which are available b... |
|
nondcesvc(4) -- file for dceping(8) that lists non-DCE services.
|
|
dceping will ping services named in nondcesvc. Supported naming conventions for this file are: + CDS Name. Example entry: /.:/hosts/foo/someService NAMESPACE PROMPT /.:/hosts/foo/someService NAMESPACE NOPROMPT You can find CDS namespace entries by using the cdsbrowser(8) command. + RPC String Binding. Example entry: ncacn_ip_tcp:foo.entity.company.com[1755] STRING_BINDING You can obtain string bin... |
|
nsswitch.conf(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... |
|
pam.conf(4) -- configuration file for pluggable authentication modules
|
|
pam.conf is the configuration file for the Pluggable Authentication Module architecture, or PAM. A PAM module provides functionality for one or more of four possible services: authentication, account management, session management, and password management. An authentication service module provides functionality to authenticate a user and set up user credentials. An account management module provid... |
|
pam_user.conf(4) -- users configuration file for pluggable authentication modules
|
|
pam_user.conf is the user configuration file for the Pluggable Authentication Module architecture, or PAM. It is not designed to replace the PAM system configuration file, pam.conf. For PAM to work properly, pam.conf is mandatory (see pam.conf(4)). pam_user.conf is optional. It is used only when a user basis configuration is needed. It mainly specifies options to be used by service modules on a us... |
|
passwd(4) -- password file
|
|
/etc/passwd contains the following information for each user: + login name + encrypted password + numerical user ID + numerical group ID + reserved gecos ID + initial working directory + program to use as shell This is an ASCII file. Each field within each user's entry is separated from the next by a colon. Each user is separated from the next by a newline. This file resides in the /etc directory... |
|
pcf(4) -- port configuration file used by DDFA software
|
|
A port configuration file is used by the Datacommunications and Terminal Controller Device File Access (DDFA) software to configure individual terminal server ports. The generic name of the template file is pcf. In practice, it is renamed for each port that needs different configuration values and the values are altered appropriately for the device attached to the port. A port configuration file i... |
|
pfs(4) -- portable file system
|
|
The Portable File System, or PFS, allows access to a variety of CD-ROM file systems. Currently supported file systems include: iso9660, high sierra, RockRidge Interchange. The PFS package consists of 7 programs: pfs_mountd is responsible for maintaining local and remote mounts. It must be running on both PFS clients and PFS servers. The pfs_mountd program validates arguments, and spawns pfs_mountd... |
|
ppp.auth(4) -- PPP authentication file format
|
|
The file /etc/ppp/Auth contains values used by HP PPP's implementation of the link-level authentication protocols, CHAP (Challenge Handshake Authentication Protocol) and PAP (Password Authentication Protocol). This implementation of both CHAP and PAP conforms to RFC 1334, PPP Authentication Protocols. CHAP is a stronger authentication mechanism and should be used whenever possible, in preference ... |
|
ppp.Auth(4) -- PPP authentication file format
|
|
The file /etc/ppp/Auth contains values used by HP PPP's implementation of the link-level authentication protocols, CHAP (Challenge Handshake Authentication Protocol) and PAP (Password Authentication Protocol). This implementation of both CHAP and PAP conforms to RFC 1334, PPP Authentication Protocols. CHAP is a stronger authentication mechanism and should be used whenever possible, in preference ... |
|
PPP.AUTH(4) -- PPP authentication file format
|
|
The file /etc/ppp/Auth contains values used by HP PPP's implementation of the link-level authentication protocols, CHAP (Challenge Handshake Authentication Protocol) and PAP (Password Authentication Protocol). This implementation of both CHAP and PAP conforms to RFC 1334, PPP Authentication Protocols. CHAP is a stronger authentication mechanism and should be used whenever possible, in preference ... |
|
ppp.devices(4) -- PPP physical device description file format
|
|
The file /etc/ppp/Devices associates dialer types with physical devices and speeds. pppd examines it when placing a call to a neighboring machine. If no suitable speed is found, or if all devices associated with that speed are busy, pppd will try again later. |
|
ppp.Devices(4) -- PPP physical device description file format
|
|
The file /etc/ppp/Devices associates dialer types with physical devices and speeds. pppd examines it when placing a call to a neighboring machine. If no suitable speed is found, or if all devices associated with that speed are busy, pppd will try again later. |
|
PPP.DEVICES(4) -- PPP physical device description file format
|
|
The file /etc/ppp/Devices associates dialer types with physical devices and speeds. pppd examines it when placing a call to a neighboring machine. If no suitable speed is found, or if all devices associated with that speed are busy, pppd will try again later. |
|
ppp.dialers(4) -- PPP dialer description file format
|
|
The file /etc/ppp/Dialers describes how to dial each type of modem attached to the UNIX system that is to be made available for outbound PPP calls. pppd examines it when placing a call to a neighboring machine. When pppd selects a line from Systems, it uses the `speed' field to select an entry in Devices, from which it uses the `dialer' field to select an entry in Dialers. pppd then interprets t... |
|
ppp.Dialers(4) -- PPP dialer description file format
|
|
The file /etc/ppp/Dialers describes how to dial each type of modem attached to the UNIX system that is to be made available for outbound PPP calls. pppd examines it when placing a call to a neighboring machine. When pppd selects a line from Systems, it uses the `speed' field to select an entry in Devices, from which it uses the `dialer' field to select an entry in Dialers. pppd then interprets t... |
|
PPP.DIALERS(4) -- PPP dialer description file format
|
|
The file /etc/ppp/Dialers describes how to dial each type of modem attached to the UNIX system that is to be made available for outbound PPP calls. pppd examines it when placing a call to a neighboring machine. When pppd selects a line from Systems, it uses the `speed' field to select an entry in Devices, from which it uses the `dialer' field to select an entry in Dialers. pppd then interprets t... |
|
ppp.filter(4) -- PPP packet filter specification file format
|
|
The file /etc/ppp/Filter describes how on-demand PPP links are to be managed. By default, any type of packet causes the link (if down) to be brought up (connected to its remote end); any packet is allowed to traverse the link; and any packet is sufficient to reset the idle timer, expiration of which would cause the link to be shut down. This combination is not always appropriate behavior, so the f... |
|
ppp.Filter(4) -- PPP packet filter specification file format
|
|
The file /etc/ppp/Filter describes how on-demand PPP links are to be managed. By default, any type of packet causes the link (if down) to be brought up (connected to its remote end); any packet is allowed to traverse the link; and any packet is sufficient to reset the idle timer, expiration of which would cause the link to be shut down. This combination is not always appropriate behavior, so the f... |
|
PPP.FILTER(4) -- PPP packet filter specification file format
|
|
The file /etc/ppp/Filter describes how on-demand PPP links are to be managed. By default, any type of packet causes the link (if down) to be brought up (connected to its remote end); any packet is allowed to traverse the link; and any packet is sufficient to reset the idle timer, expiration of which would cause the link to be shut down. This combination is not always appropriate behavior, so the f... |
|
ppp.keys(4) -- PPP encryption keys file format
|
|
The keys file named in the gw-crypt option on the pppd command line contains key values used by HP PPP's implementation of link-level encryption. Before transmission, packets with source and destination addresses matching the endpoints on a keys file line are encrypted using DES with the key specified on that keys file line. Upon reception, packets with source and destination addresses matching t... |
|
ppp.Keys(4) -- PPP encryption keys file format
|
|
The keys file named in the gw-crypt option on the pppd command line contains key values used by HP PPP's implementation of link-level encryption. Before transmission, packets with source and destination addresses matching the endpoints on a keys file line are encrypted using DES with the key specified on that keys file line. Upon reception, packets with source and destination addresses matching t... |
|
PPP.KEYS(4) -- PPP encryption keys file format
|
|
The keys file named in the gw-crypt option on the pppd command line contains key values used by HP PPP's implementation of link-level encryption. Before transmission, packets with source and destination addresses matching the endpoints on a keys file line are encrypted using DES with the key specified on that keys file line. Upon reception, packets with source and destination addresses matching t... |
|
ppp.systems(4) -- PPP neighboring systems description file format
|
|
The file /etc/ppp/Systems describes how to connect with neighboring systems via PPP. |
|
ppp.Systems(4) -- PPP neighboring systems description file format
|
|
The file /etc/ppp/Systems describes how to connect with neighboring systems via PPP. |
|
PPP.SYSTEMS(4) -- PPP neighboring systems description file format
|
|
The file /etc/ppp/Systems describes how to connect with neighboring systems via PPP. |
|
pppoec.conf(4) -- PPPoE (Point to Point Protocol over Ethernet) client configuration file
|
|
pppoec.conf is the configuration file for the pppoec daemon. This file is read by pppoec to initialize the client. The default file is /etc/ppp/pppoec.conf. Note that, you cannot run pppoec without this configuration file. Each entry in the pppoec.conf file is separated by a new line. Blank lines and lines that begin with # are ignored. |
|
pppoerd.conf(4) -- PPPoE (Point to Point Protocol over Ethernet) relay configuration file
|
|
pppoerd.conf is the configuration file for the pppoerd daemon. This file is read by pppoerd to initailize the relay. The default file is /etc/ppp/pppoerd.conf. Note that, you cannot run pppoerd without this configuration file. Each entry in the pppoerd.conf file is separated by a new line. Blank lines and lines that begin with # are ignored. |
|
pppoesd.conf(4) -- PPPoE (Point to Point Protocol over Ethernet) server configuration file
|
|
pppoesd.conf is the configuration file for the pppoesd daemon. This file is read by pppoesd to initialize the server. The default file is /etc/ppp/pppoesd.conf. You can use this file to set parameters for each network interface used by pppoesd during PPPoE sessions. Each entry in the pppoesd.conf file is of the following format: parameter=value Each entry in the configuration file is separated by ... |
|
privgrp(4) -- format of privileged values
|
|
setprivgrp() sets a mask of privileges, and getprivgrp(2) returns an array of structures giving privileged group assignments on a pergroup-ID basis (see getprivgrp(2)). setprivgrp() associates a kernel capability with a group ID. This allows subletting of superuser-like privileges to members of a particular group or groups. The constants and structures needed for these system calls are defined in ... |
|
profile(4) -- set up user's environment at login time
|
|
If the file /etc/profile exists, it is executed by the shell for every user who logs in. The file /etc/profile should be set up to do only those things that are desirable for every user on the system, or to set reasonable defaults. If a user's login (home) directory contains a file named .profile, that file is executed (via the shell's exec .profile) before the session begins. .profile files are... |
|
proto(4) -- prototype job file for at(1)
|
|
When a job is submitted to at or batch, the job is constructed as a POSIX shell script (see at(1)). The job file is created in /var/spool/cron/atjobs as follows: + at creates a header describing the job as an at job or a batch job. at jobs submitted to all queues other than queue a are listed as batch jobs. The header is: : at job for an at job, or : batch job for a batch job. + A set of POSIX she... |
|
protocols(4) -- protocol name data base
|
|
This file associates protocol numbers with official protocol names and aliases. This allows the user to refer to a protocol by a symbolic name instead of a number. For each protocol a single line should be present with the following information: These mappings are defined in RFC 1700 Assigned Numbers. Aliases are other names under which... |
|
prpwd(4) -- protected password authentication database files used for trusted systems
|
|
An authentication profile is maintained for each user on the system. A user profile is kept in a protected password database file that is accessible only to the System Administrator. The protected password database files contain among other things the encrypted password for the user account. On a trusted system, the passwords are hidden from normal users. The protected password database files do n... |
|
publickey(4) -- public key database
|
|
/etc/publickey is a local public key database that is used for secure RPC. The /etc/publickey file can be used in conjunction with or instead of other publickey databases, including the NIS publickey map and the NIS+ publickey map. Each entry in the database consists of a network user name (which may refer to either a user or a hostname), followed by the user's public key (in hex notation), a col... |
|
queuedefs(4) -- queue description file for at, batch, and crontab
|
|
The queuedefs file describes the characteristics of the queues managed by cron (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[.[njobj][j][nicen][n][nwaitw] The fields in this line are: w] The fields in this line are: q The name of the queue, such that a is the default queue for jobs started by at (see at(1)), b is the queue for jo... |
|
rc.config(4) -- files containing system configuration information
|
|
The system configuration used at startup is contained in files within the directory /etc/rc.config.d. The file /etc/rc.config sources all of the files within /etc/rc.config.d and /etc/TIMEZONE and exports their contents to the environment. /etc/rc.config The file /etc/rc.config is a script that sources all of the /etc/rc.config.d/* scripts, and also sources /etc/TIMEZONE. To read the configuration... |
|
rc.config.d(4) -- files containing system configuration information
|
|
The system configuration used at startup is contained in files within the directory /etc/rc.config.d. The file /etc/rc.config sources all of the files within /etc/rc.config.d and /etc/TIMEZONE and exports their contents to the environment. /etc/rc.config The file /etc/rc.config is a script that sources all of the /etc/rc.config.d/* scripts, and also sources /etc/TIMEZONE. To read the configuration... |
|
rcsfile(4) -- format of RCS files
|
|
An RCS file is an ASCII file. Its contents are described by the grammar below. The text is free format, i.e., spaces, tabs and newline characters have no significance except in strings. Strings are enclosed by @ symbols. If a string contains the @ symbol, the symbol must be doubled. The meta syntax uses the following conventions: | (bar) Separates alternatives. {...} (braces) Encloses optional phr... |
|
resolv.conf(4) -- resolver configuration file
|
|
The resolver is a set of routines in the C library (see resolver(3N)) that provide access to the Internet Domain Name System. The resolver configuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human-readable, and contains a list of keywords with values that provide various types of resolver information... |
|
resolver(4) -- resolver configuration file
|
|
The resolver is a set of routines in the C library (see resolver(3N)) that provide access to the Internet Domain Name System. The resolver configuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human-readable, and contains a list of keywords with values that provide various types of resolver information... |
|
rhosts(4) -- security files authorizing access by remote hosts and users on local host
|
|
The /etc/hosts.equiv file and files named .rhosts found in users' home directories specify remote hosts and users that are "equivalent" to the local host or user. Users from equivalent remote hosts are permitted to access a local account using rcp or remsh or to rlogin to the local account without supplying a password (see rcp(1), remsh(1), and rlogin(1)). The security provided by hosts.equiv i... |
|
rmtab(4) -- local file system mount statistics
|
|
File /etc/rmtab contains a record of all clients that mounted remote file systems from this machine. Whenever a remote mount is done, an entry is made in the rmtab file of the machine serving that file system. umount removes the entry of a remotely mounted file system. umount -a broadcasts to all servers that they should remove all entries from rmtab created by the sender of the broadcast message.... |
|
rndc.conf(4) -- rndc configuration file
|
|
The BIND utility for controlling the name server, rndc, has its own configuration file /etc/rndc.conf. This file has a structure and syntax similar to that of named's configuration file, named.conf. Statements are enclosed in braces and terminated with a semi-colon. Clauses in the statements are also semi-colon terminated. The usual comment styles supported are: C style: /* */ C++ style: // to en... |
|
rpc(4) -- rpc program number data base
|
|
File /etc/rpc contains user-readable names that can be used in place of RPC program numbers. Each line has the following information: + Name of server for the RPC program + RPC program number + Aliases Items are separated by any number of blanks and tab characters. A # anywhere in the file indicates a comment extending to the end of that line. |
|
rtradvd.conf(4) -- configuration file for router advertisement daemon
|
|
This file describes the information used by rtradvd(1M) when constructing IPv6 router advertisement packets for a specific interface as specified by RFC 2461 ("Neighbor Discovery for IP Version 6"). This file is read by rtradvd at initialization time or upon reception of signal SIGHUP. rtradvd configuration consists of two general statements (defaults, interface) and one substatement (prefixinfo... |
|
sccsfile(4) -- format of SCCS file
|
|
An SCCS file is an ASCII file consisting of six logical parts: checksum Sum of all characters in the file except the first line. delta table Contains information about each delta. user names Login names and/or numerical group IDs of users who are allowed to add deltas. flags Definitions of internal keywords. comments Arbitrary descriptive information about the file. body Actual text lines intermix... |
|
sd(4) -- all objects that Software Distributor (SD) uses, their attributes and storage formats
|
|
The SD commands create, install, distribute and manage software objects (bundles, products, subproducts and filesets). In addition, they define and manage other objects in support of the software administration tasks which users perform. This manual page describes the SD software object classes, their attributes, and the file formats used to store their definitions. For an overview of all SD comma... |
|
securenets(4) -- NIS map security file
|
|
The /etc/securenets file defines networks and hosts that may access the NIS maps on a server. Each line in the file gives a network mask and a net address, each in dotted quad format. For example: 255.255.255.255 133.33.33.33 The file may have any number of netmask/net pairs. When ypserv is started on the server, it checks for the existence of /etc/securenets and reads its contents into memory if ... |
|
security(4) -- security defaults configuration file
|
|
A number of system commands and features are configured based on certain parameters defined in the /etc/default/security configuration file. This file must be world readable and root writable. Each line in the file is treated either as a comment or as configuration information for a given system command or feature. Comments are denoted by a # at the beginning of a line. Noncomment lines are of the... |
|
services(4) -- service name data base
|
|
The file /etc/services associates official service names and aliases with the port number and protocol the services use. For each service a single line should be present with the following information: Port numbers 0 through 1023 are assigned by RFC 1700. This RFC also lists the conventional use of various ports with numbers greater tha... |
|
services.window(4) -- file containing applications and their associated memory window id
|
|
The files /etc/services.window is used by applications using memory windows. Each line in the /etc/services.window file associates an application with a memory window id. A line in the /etc/services.window file cannot start with a space or tab. The format is a unique name, defining the application, followed by a space/tab, followed by a unique window_id. See the sample file in EXAMPLES. Memory win... |
|
shadow(4) -- shadow password file
|
|
The /etc/shadow file is created from the /etc/passwd file by the pwconv command. It is readable only by a privileged user. It can be modified by the passwd, useradd, usermod, and userdel commands. Programs may use the interfaces described in the getspent(3C) manpage to access this information. These functions return a pointer to an spwd structure, which is defined in the header file. |
|
shells(4) -- list of allowed login shells
|
|
/etc/shells is an ASCII file containing a list of legal shells on the system. Each shell is listed in the file by its absolute path name. Lines or portions of lines beginning with # are assumed to be comments and are ignored. Blank lines are also ignored. |
|
slp.conf(4) -- Configuration file for SLP Agents
|
|
The /etc/slp.conf file contains various configuration options for the agents which include the clients that use SLP APIs, the Service Agent server and Directory agents. It determines the configuration of all the SLP agents running on that host. The SLP SA server and DA read the slp.conf file during their invocation and also when they are reconfigured by sending the SIGHUP signal. The properties sp... |
|
slp.reg(4) -- SLP static registration file
|
|
The /etc/slp.reg file provides a mechanism for old applications which are not SLP enabled and cannot be converted, and for portably exchanging registrations between SLP implementations. This file contains a list of service registrations that are read by slpd at startup time and advertised later by slpd which can be acting either as the service agent server or the directory agent. The character enc... |
|
sm(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 ... |
|
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... |
|
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 ... |
|
vol_pattern(4) -- VERITAS Volume Manager disk group search specifications
|
|
The vol_pattern search expression language can be used in vxprint and vxedit, and with some VERITAS Volume Manager (VxVM) support library functions, to locate VERITAS Volume Manager configuration records with particular characteristics. Searches are limited to operation on one disk group at a time. In the current release, search expressions are limited to volume, plex, subdisk, DCO and snap record... |
|
vxmake(4) -- format of a vxmake description file
|
|
Descriptions of configuration records can be given to the vxmake utility either on the command line or in a file. Descriptions given on the command line can specify only one new record. Descriptions given in a description file can specify more than one record. The description file format is a convenient way of indicating record contents for other uses as well. For example, the vxprint utility can ... |
|
wellknownif(4) -- file for dceping(8) that contains the well-known interface IDs for core DCE and other services.
|
|
The default file contains core DCE services. Do not delete those entries. You can edit the file to include other services. The format of an entry is: server_name interface_id major_version_number minor_version_number You can obtain interface_id from the IDL header file for the server. Blank lines or lines beginning with # are ignored. You can use either spaces or tabs to separate items in a line. ... |
|
wtmp(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];... |
|
wtmps(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... |
|
xtab(4) -- directories to export to NFS clients
|
|
File /etc/exports describes the directories that can be exported to NFS clients. The system administrator creates it using a text editor. mountd processes it each time a mount request is received (see mountd(1M)). /etc/exports is read automatically by the exportfs command (see exportfs(1M)). If this file is changed, exportfs must be run (exportfs -a) before the changes can affect the daemon's ope... |
|
ypfiles(4) -- Network Information Service database and directory structure
|
|
Remarks The Network Information Service (NIS) was formerly known as Yellow Pages (yp). Although the name has changed, the functionality of the service remains the same. The Network Information Service (NIS) network lookup service uses databases in the directory hierarchy under /var/yp. These databases exist only on machines that act as NIS servers. A database consists of two files created by maked... |
