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