|
|
|
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(... |
