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